Tracking formal deliverables across project phases allows teams to monitor progress, identify gaps, and manage delivery timelines in enterprise IT projects. Assigning each deliverable to a specific role creates accountability and sets clear expectations, supporting effective delivery across Waterfall, Scrum, SAFe, and Hybrid models.
Enterprise IT projects produce a wide range of formal deliverables. Teams manage these outputs using tools such as a formal deliverables inventory and a formal deliverables roadmap. These tools improve visibility of deliverable status, dependencies, and timelines.
Formal Deliverables Inventory
The formal deliverables inventory records and monitors key outputs in enterprise IT projects. It lists each deliverable, assigns responsible roles, and tracks delivery status to support accountability and visibility. Teams apply the inventory across delivery models, as shown in the following examples:
- Waterfall application: In a system implementation project, the inventory tracks business requirements documents, technical specifications, and test result reports to maintain oversight of outputs during each project phase.
- Agile (Scrum or SAFe) application: In a Scrum-based application development project, the inventory records user stories, sprint backlogs, and incremental deliverables.
- Hybrid model application: In projects that include application development and infrastructure upgrades, the inventory tracks Waterfall-based infrastructure specifications alongside Agile-based incremental deliverables.
Table 20 presents a partial inventory of key deliverables for a Waterfall project. This table specifies the accountable role for each deliverable and its delivery status. Additional tracking details, such as Start Date, Target Completion Date, Review Status, Approval Status, Date Approved, and Latest Version, can be included as needed.
| Discipline | Role Title | Accountable Person | Formal Deliverables | Delivery Status |
|---|---|---|---|---|
| Program management | Program Manager | Tim Lin | Program plan | Done |
| Project management | Project Manager | Seth Dunn | Project plan | In progress |
| Scheduling | Master Scheduler | Miles Stone | Project schedule | In Progress |
| Solution architecture | Solution Architect | Archie Teck | Solution architecture document | In Progress |
| Business analysis | Business Analyst | Claire Scope | Business analysis plan | In Progress |
| Business analysis | Business Analyst | Claire Scope | Business requirements document | In Progress |
| Business analysis | Business Analyst | Rick Quire | Non-functional requirements | Not Started |
| Business analysis | Business Analyst | Rick Quire | Functional requirements | Not Started |
| Process analysis | Process Analyst | Flo Charter | Process maps | Not Started |
Formal Deliverables Roadmap
The formal deliverables roadmap shows the timeline, dependencies, and responsible roles for each deliverable. This tool supports coordination in projects with complex schedules and multiple disciplines by aligning teams on sequencing and milestone timing. Teams apply the roadmap across delivery models, as shown in the following examples:
- Waterfall application: In a system implementation project, the roadmap plots business requirements documents, technical specifications, and test result reports across linear phases, identifying dependencies that could cause delays.
- Agile (Scrum or SAFe) application: In a Scrum-based application development project, the roadmap tracks user stories, sprint backlogs, and incremental deliverables across sprints.
- Hybrid model application: In projects that combine application development with infrastructure upgrades, the roadmap integrates Waterfall-based infrastructure specifications and Agile-based deliverables to map dependencies and support coordinated delivery.
Figure 10 illustrates a partial roadmap for a Waterfall project, detailing disciplines, deliverable timelines, deliverables within project phases, and dependencies.
