Every participant is expected to contribute at least one project deliverable in enterprise IT projects. If a project role does not produce a deliverable, it is an unnecessary overhead—except for business stakeholder roles in projects. While business stakeholders do not create tangible deliverables, they provide valuable information, feedback, advice, and direction to the project.
Understanding the link between roles and their respective deliverables is essential in enterprise IT projects. This clarity helps recognise each participant's value and contributions to project delivery.
Deliverables in Waterfall Projects
The Waterfall model, with its structured, phase-based approach, relies on expert discipline at every stage of the project lifecycle:
- Detailed planning: Ensures every aspect of the project is considered before work begins, minimising risks and providing participants with a clear understanding of their roles.
- Documentation: Establishes a comprehensive audit trail detailing what was done, why, and by whom. This is vital for maintaining quality and supports future maintenance and enhancements.
- Defined roles and responsibilities: Each team member knows their specific contributions, reducing overlap and enhancing efficiency throughout the project lifecycle.
Table 16 categorises the fundamental disciplines contributing to Waterfall projects, outlines the specific roles within those disciplines, and lists the key deliverables associated with each role.
Table 16. Key Project Deliverables by Discipline and Role in Waterfall Projects
| Discipline | Role Title | Deliverable |
|---|---|---|
| Programme management | Programme Manager | Programme plan, Milestone reports |
| Project management | Project Manager | Project plan, Risk register |
| Project analysis | Project Analyst | Project analysis reports, Requirement traceability matrix |
| Scheduling | Master Scheduler | Project schedule, Resource allocation plan |
| Project assurance | Project Assurance Manager | Quality Assurance reports and compliance documentation |
| Risk management | Risk Manager | Risk management plan, Risk log |
| Compliance management | Compliance Manager | Compliance audit reports, Regulatory compliance checklist |
| Solution architecture | Solution Architect | Solution design documents, Architecture decisions |
| Business analysis | Business Analyst | Business Requirements Document, Functional specifications |
| Organisational change management | Change Manager | Change management strategy, Stakeholder analysis |
| Process analysis | Process Analyst | Process maps, Improvement recommendations |
| Data architecture | Data Architect | (No deliverables provided) |
| Data analysis | Data Analyst | Data analysis reports, Data quality assessments |
| User experience | UX/UI Designer | User research reports and wireframes |
| System architecture | System Architect | (No deliverables provided) |
| System design | System Designer | Design specifications, System models |
| System analysis | System Analyst | System requirements document, System gap analysis |
| System development | Developer | Source code, Deployment packages |
| Environment management | Environment Manager | Environment setup plan, Environment status reports |
| Release management | Release Manager | Release plan, Deployment checklist |
| Test management | Test Manager | Test strategy, Automated test suites |
| Implementation management | Implementation Manager | Implementation plan, Go-Live checklist |
Deliverables in Scrum Projects
The Scrum framework values discipline expertise and operates on principles that support broader skill application within the team:
- Self-organisation: Allows fluidity in team roles and tasks and sprint objectives.
- Cross-functionality: Promotes skill diversification. For example, while a backend developer primarily focuses on their expertise, they may also engage in front-end tasks as needed.
- Skill expansion: Build a versatile team capable of adapting to various project roles.
Table 17 below illustrates how each discipline translates into the Scrum project delivery model, including role titles and key deliverables. Notes are provided where specific disciplines do not directly align with Scrum roles.
Table 17. Key Project Deliverables by Discipline and Role in Scrum Projects
| Discipline | Role Titles | Deliverables |
|---|---|---|
| Programme management | Not defined under Scrum | - |
| Project management | Scrum Master | Sprint backlog, Burndown charts |
| Project analysis | Not explicitly defined under Scrum | Roles merge into Scrum roles with overlapping responsibilities |
| Scheduling | Scrum Master | Sprint planning, Velocity tracking |
| Project assurance | Integrated into Scrum roles | Quality Assurance practices documentation, Compliance checklists |
| Risk management | Scrum Master, Product Owner | Sprint risk assessments, Risk mitigation strategies |
| Compliance management | Product Owner | Compliance audit logs, Regulatory alignment documentation |
| Solution architecture | Development Team Member (Solution Architect) | Architectural decisions, System design documentation |
| Business analysis | Product Owner | Product backlog, User story mapping |
| Organisational change management | Scrum Master, Agile Coach | Team coaching plan, Agile adoption metrics |
| Process analysis | Not defined under Scrum | - |
| Data architecture | Data Architect | (No deliverables provided) |
| Data analysis | Integrated into Scrum roles | Roles merge into Scrum roles with overlapping responsibilities |
| User experience | Development Team Member (UX/UI Designer) | Interactive prototypes, Accessibility compliance checks |
| System architecture | System Architect | System architecture |
| System design | Development Team Member (System Designer) | Design specifications, Usability guidelines |
| System analysis | Development Team (System Analyst) | System requirements analysis, Performance benchmarks |
| System development | Development Team Member (Developer) | Incremental builds, Code review feedback |
| Environment management | Development Team Member (DevOps) | Environment setup guidelines, Deployment scripts |
| Release management | Scrum Master | Sprint release plan, Release retrospectives |
| Test management | Development Team Member (Tester) | Test-driven development outputs, Sprint test reports |
| Implementation management | Not defined under Scrum | - |
Deliverables in SAFe Projects
The Scaled Agile Framework emphasises a structured, scalable approach to project delivery that integrates discipline expertise across multiple team levels:
- Aligned planning: Ensures teams at various levels (team, programme, and portfolio) synchronise their objectives and timelines, supporting cohesive strategic execution.
- Role specialisation: Encourages clear delineation of responsibilities, enhancing accountability and clarity across the project. For example, a Release Train Engineer focuses on orchestrating the Agile Release Train, ensuring seamless integration of outputs from different teams.
- Continuous improvement: Evolve project competencies and maximise efficiency through regular reflection and adaptation cycles.
Table 18 below details how various disciplines are incorporated into the SAFe project delivery model, listing specific roles and their key deliverables. Explanations are provided where disciplines do not have a direct match in SAFe roles.
Table 18. Key Project Deliverables by Discipline and Role in SAFe Projects
| Discipline | Role Titles | Deliverables |
|---|---|---|
| Programme management | Release Train Engineer (RTE) | Program Increment (PI) Objectives, PI Planning outputs |
| Project management | Scrum Master, Agile Project Manager | Sprint backlog, Burndown charts |
| Project analysis | Not explicitly defined under SAFe | Roles merge into Scrum/Agile Project Manager roles with overlapping responsibilities. |
| Scheduling | Agile Release Train Engineer (RTE) | PI timelines, Capacity planning |
| Project assurance | Integrated into SAFe roles | Quality Assurance plans and compliance reports. |
| Risk management | Risk Manager, Agile Coach | Risk burndown chart, Risk retrospectives |
| Compliance management | Product Management and System Architects | Compliance artifacts, Governance compliance checks |
| Solution architecture | System Architect, Agile Team Member (Architect) | Architectural runway, System and solution architecture documentation |
| Business analysis | Business Analyst | Epic User stories, Feature breakdown |
| Organisational change management | Lean-Agile Change Agent | Change management plan, Lean-Agile transformation roadmap |
| Process analysis | Not defined under SAFe | - |
| Data architecture | Data Architect | (No deliverables provided) |
| Data analysis | Data Analyst | Data-driven decision frameworks, Agile data strategies |
| User experience | Agile Team Member (UX/UI Designer) | Design sprints, Usability test results, UI/UX prototypes, Design sprint outputs |
| System architecture | System Architect | (No deliverables provided) |
| System design | Agile Team Member (System Designer) | High-level system designs, Interface specifications |
| System analysis | Agile Team Member (System Analyst) | System analysis documentation, Integration documentation |
| System development | Agile Team Member (Developer) | Incremental builds, Pair programming output |
| Environment management | Environment Manager, DevOps Engineer | Environment provisioning guidelines, Deployment pipeline automation |
| Release management | Release Train Engineer, Release Manager | Release strategy, Go-Live plan |
| Test management | Agile Team Member (Tester) | Test-driven development outputs, Sprint test reports |
| Implementation management | Not defined under SAFe | - |
Deliverables in Hybrid Projects
The Hybrid model blends traditional and Agile methodologies, allowing flexibility in applying discipline expertise based on project demands:
- Flexible role adaptation: Allows participants to shift between traditional and Agile practices, choosing tasks that suit the project phase and their skill sets, enhancing adaptability and effectiveness.
- Integration of methodologies: Enables team members to work on tasks requiring a Waterfall approach for defined stages and outcomes while engaging in iterative, sprint-based tasks where quick adaptations are beneficial.
- Enhanced skill versatility: Prepares the team to handle various project requirements, adapting their approach as needs evolve.
Table 19 below outlines how each discipline is implemented in the Hybrid project delivery model, specifying the roles and key deliverables.
Table 19. Key Project Deliverables by Discipline and Role in Hybrid Projects
| Discipline | Role Titles | Deliverables |
|---|---|---|
| Programme management | Programme Manager | Integrated programme plans, Milestone reports |
| Project management | Project Manager | Hybrid project plan, Risk register, Sprint backlog |
| Project analysis | Project Analyst | Project analysis reports |
| Scheduling | Scheduler | Integrated project schedule, Resource allocation plan |
| Project assurance | Quality Assurance Lead | Quality Assurance plans, Compliance audits |
| Risk management | Risk Manager | Risk management plan, Risk log, Risk burndown charts |
| Compliance management | Compliance Manager | Compliance documentation, Regulatory compliance updates |
| Solution architecture | Not typically distinguished | Role integrated into development and design deliverables |
| Business analysis | Business Analyst | Business Requirements Document, User stories |
| Organisational change management | Change Manager | Change management strategy, Stakeholder analysis |
| Process analysis | Not typically distinguished | Role integrated into change management and business analysis deliverables |
| Data architecture | Data Architect | (No deliverables provided) |
| Data analysis | Data Analyst | Data analysis reports, Data-driven decision frameworks |
| User experience | UX/UI Designer | User research reports, Wireframes, Usability test results, Design specifications, UI/UX prototypes |
| System architecture | System Architect | (No deliverables provided) |
| System design | Integrated into Development roles | High-level system designs, Interface specifications integrated into development deliverables |
| System analysis | System Analyst | System analysis reports, Integration documentation |
| System development | Developer | Source code, Incremental builds, Pair programming output |
| Environment management | Integrated into IT Operations roles | Environment setup and management guidelines, integrated into operations planning |
| Release management | Release Manager | Release plan, Deployment checklist, Go-Live plan |
| Test management | Tester Manager, Test Lead, Test Analyst | Test strategy, Automated test suites, Sprint test reports |
| Implementation management | Not typically distinguished | Role and deliverables integrated into project management and release management |
