Glossary Term | Description |
Accountability Details | An overview of the team accountable details and how the deliverable progress is tracking details related to a deliverable. |
Accountable Team | The department accountable for a specified deliverable. Identifying the department will assist in holding them accountable. The chosen department is accountable for completing the work within the deliverable. |
Completion Status | The actual percentage completed as updated by the owner or project manager. |
Deliverable ID | A unique identifier generated and assigned to a deliverable when created and saved. |
Deliverable Status | The current status of a deliverable. PMs can refer to this field to assess the progress of a deliverable. The status types include: * Not started - work on the deliverable has not commenced * Delayed - deliverable is not completed and end date in the past * Expected delay - deliverable is not completed but end date in the future * On target - deliverable in-progress and expected to be completed by the due date * Completed- The Activity is 100% completed |
Deliverables | Deliverable is a tangible and measurable piece of work that is completed, approved and delivered at a point of time. Creating the deliverables helps with communication and tracking purposes and should be defined at the beginning of the project. |
End Date | The date when this deliverable must be completed and delivered by. The deliverable will usually need to have completed its planning, draft, review and approval before being delivered. |
General | A general summary of details related to a deliverable. This is useful for PMs to ensure a project is executed efficiently and promptly. Details of the deliverable can be easily obtained by users through this section. Thus, providing them with a good understanding of the deliverable. |
Name | A short title which clearly defines the deliverable which can be understood by all readers. |
Notes | The findings from the deliverable review which provides other project members with visibility around deliverable updates. Thus, project members are able to execute plans in unison and with greater efficiency. |
Project Phase | The phase of the project during which the deliverable is expected to be completed. |
Quality Assessment | Results and findings of a Quality Assessment Review of the Deliverable. It is important to highlight any current or potential issues related to the deliverable. PMs can use the information from this section to implement mitigation measures to ensure a deliverable is executed effectively. |
Quantity | The number of deliverables required to be completed in order to fully complete the deliverable. |
Resource Availability | The status of the Resource Availability can fall under 3 categories: * Working- 100% full capacity * Under-resourced by half- 50% or more capacity not available * Under-resourced by a quarter- 25% required resources not available |
Review Date | The date the deliverable reviewed and updated. |
Start Date | The deliverable start date is either sourced from the task start date in the schedule (Automatic) or date the deliverable was manually created in the Deliverable Module (Manual). |
Status | The current status of a deliverable. PMs can refer to this field to assess the progress of a deliverable. The status types include: * Not started - work on the deliverable has not commenced * Delayed - deliverable is not completed and end date in the past * Expected delay - deliverable is not completed but end date in the future * On target - deliverable in-progress and expected to be completed by the due date * Completed- The Activity is 100% completed |
Type | Deliverable type options are Manual or Automatic. A deliverable can be created manually within the module (Manual) or a task marked in the schedule as a deliverable (Automatic). For Automatic the WBS reference is also displayed. |
Updates | Audit log of all changes made to the deliverable |
User | Name of the project member who conducted the review and updated the deliverable. |
Work Stream | Workstreams are core areas of activities in your project. Could be a department in your organization (i.e Operations or Marketing) or an ongoing activity in your project (i.e Testing or Implementation)" |
1.12 Deliverables Glossary Print
Created by: Charisse Abillero
Modified on: Mon, 23 Nov, 2020 at 8:13 PM
Did you find it helpful? Yes No
Send feedbackSorry we couldn't be helpful. Help us improve this article with your feedback.