In PRINCE2 7, a delivery approach defines how the products of a project will be created and implemented. It represents the method or combination of methods chosen to develop, build, and hand over the project's outputs to the customer or end users.
PRINCE2 7 recognizes that different projects requi…In PRINCE2 7, a delivery approach defines how the products of a project will be created and implemented. It represents the method or combination of methods chosen to develop, build, and hand over the project's outputs to the customer or end users.
PRINCE2 7 recognizes that different projects require different ways of working, and the framework is designed to integrate with various delivery approaches rather than prescribing a single method. The three main categories of delivery approaches are:
1. Linear (Waterfall): This traditional approach follows a sequential process where each phase must be completed before the next begins. Requirements are gathered upfront, and the product is delivered at the end of the project. This works well when requirements are clear and unlikely to change.
2. Iterative and Incremental: Products are developed through repeated cycles (iterations), with each cycle building upon previous work. Increments are partial deliveries of the final product, allowing users to benefit from functionality before the entire project completes.
3. Agile: This approach embraces flexibility and collaboration, responding to changing requirements throughout the project. Work is organized into short timeboxes, delivering working products frequently while continuously gathering feedback.
PRINCE2 7 can work alongside any of these approaches. The project management layer (provided by PRINCE2) handles governance, controls, and decision-making, while the delivery approach handles the technical work of creating products.
When selecting a delivery approach, project teams should consider factors such as the nature of the product, how well requirements are understood, the level of stakeholder involvement available, organizational culture, and regulatory constraints.
The chosen delivery approach influences how stages are structured, how progress is monitored, and how products are accepted. PRINCE2 7's flexibility allows organizations to tailor the framework to complement their preferred delivery methods effectively.
Delivery Approaches in PRINCE2
What are Delivery Approaches?
A delivery approach defines the way in which products are developed and handed over during a project. In PRINCE2, the delivery approach determines how the specialist work will be organized and executed to create the project's outputs. This could range from traditional linear methods to iterative and incremental approaches, or even hybrid combinations.
Why are Delivery Approaches Important?
Understanding delivery approaches is crucial because:
• They influence how the project is planned, monitored, and controlled • The choice of approach affects stage boundaries, checkpoints, and review points • Different products within the same project may require different delivery approaches • The approach must align with organizational capabilities and project characteristics • Selecting the wrong approach can lead to project failure or inefficiency
Types of Delivery Approaches
Linear (Waterfall): Work progresses through sequential phases where each phase must be completed before the next begins. Best suited for projects with well-defined requirements and stable environments.
Iterative: Products are developed through repeated cycles, with each iteration refining and improving upon the previous version. Useful when requirements may evolve.
Incremental: The final product is delivered in portions or increments, with each increment adding functionality. Allows early delivery of partial benefits.
Agile/Hybrid: Combines elements of different approaches. PRINCE2 can work alongside agile methods, with PRINCE2 providing governance and agile methods handling delivery.
How Delivery Approaches Work in PRINCE2
PRINCE2 is flexible regarding delivery approaches. The project management method (PRINCE2) wraps around whatever delivery approach is chosen for the specialist work. Key considerations include:
• The delivery approach is defined during the Starting up a Project process • It is documented in the Project Initiation Documentation (PID) • Stage planning must accommodate the chosen delivery approach • Work packages are tailored based on how products will be delivered • Progress reporting and controls adapt to suit the approach
Factors Influencing the Choice of Delivery Approach
• Nature and complexity of the products being created • Organizational standards and capabilities • Customer requirements and involvement preferences • Regulatory or compliance requirements • Level of requirement certainty • Available skills and resources • Risk tolerance
Exam Tips: Answering Questions on Delivery Approaches
Key Points to Remember:
1. PRINCE2 does not mandate a specific delivery approach - it is adaptable to any method
2. The delivery approach is concerned with how products are created, while PRINCE2 provides the project management framework
3. Different products in the same project can use different delivery approaches
4. The approach should be determined early in the project during Starting up a Project
5. The Project Initiation Documentation captures the chosen delivery approach
Common Exam Question Themes:
• Identifying which delivery approach suits a given scenario • Understanding that PRINCE2 separates project management from product delivery • Recognizing that the approach affects planning and control mechanisms • Knowing where delivery approach information is documented
Exam Strategy:
When answering questions, focus on the principle that PRINCE2 provides governance and direction while remaining neutral about how specialist work is performed. Look for answers that emphasize flexibility and tailoring rather than rigid adherence to one method. Remember that the project context should drive the choice of delivery approach, not the other way around.