Project Deliverables

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 the Waterfall Model

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 15 categorises the fundamental disciplines contributing to Waterfall projects, outlines the specific roles within those disciplines, and lists the key deliverables associated with each role.

Deliverables in the Scrum Model

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 back-end 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 16 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.

Deliverables in the SAFe Model

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 17 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.

Deliverables in the Hybrid Model

The Hybrid model blends Waterfall and Agile approaches, allowing flexibility in applying discipline expertise based on project demands. Unlike Waterfall, Scrum, or SAFe, which define fixed roles and deliverables, the Hybrid approach adapts based on project complexity, phase, and organisational needs.

• 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. Roles may take on different responsibilities depending on project requirements.
• 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. This adaptability ensures deliverables align with the best-fit approach.
• Enhanced skill versatility: Prepares the team to handle various project requirements, adapting their approach as needs evolve. This allows disciplines to be implemented based on necessity rather than predefined structures. 

Table 18 reflects the Hybrid model's adaptive nature, showing how each discipline may align with Waterfall, Agile, or a combination of both. It provides guidance rather than a fixed role-to-deliverable mapping, allowing flexibility in how responsibilities are assigned and outputs are delivered.