The Tasks page shows all of the deliverables for the project you are currently viewing. From this page, you can subscribe to, and reference a deliverable. Only project or program managers can create a deliverable. Project or program managers and the deliverable owner can edit a deliverable.

Deliverables represent the tangible or measurable output of a project or program, for example, a document that is to be delivered by a specific date. Deliverables might represent design models, specification documents, prototypes, tooling modifications, and reports. In many cases, deliverables are the most important piece of project or program information to manage and track. Most activities and milestones are ultimately created and executed in order to support the completion of deliverables.

Deliverables can be associated with objects such as documents, parts, activities and milestones, essentially linking the items together. In this way, multiple deliverables are associated with a single item, a single deliverable is associated with multiple items, or a deliverable exists as an item unassociated with any other items. These deliverables are typically created as assignments and managed as part of the project plan. For example, you might associate an activity to a deliverable as the one whose work is responsible for producing the deliverable. Or you might track a whole set of deliverables independent of the activities to which they belong by associating them with a specific milestone.

The estimated finish date is calculated from children to parent. Deliverables are considered children of activities, so the estimated finish date of an activity is calculated based on its associated deliverable.

Several deliverables may be associated with the same milestone, and the same deliverable can be associated with two separate milestones. A single deliverable should be associated at most to one activity.

A deliverable reaches an execution state of complete when it is marked as 100% done.