Choose a delivery context

What you will understand

• Distinguish linear, iterative-incremental and hybrid delivery.
• Identify contextual factors that shape management arrangements.
• Separate management stages from specialist delivery cycles.

The idea

Two projects can follow the same management principles while creating their products very differently. One may need a fixed physical sequence, another may learn through small releases and another may combine both. Before choosing the management arrangements, understand what is being delivered, how uncertain the requirements are and which organisational or commercial boundaries the work must cross.

A linear approach tends to progress through planned specialist phases, with substantial work in one phase preceding the next. It can suit a product whose sequence and requirements are sufficiently understood. Iterative work revisits and refines a solution through feedback. Incremental work adds usable parts over time. Teams often combine iteration and increments, but the terms describe different ideas: refinement and addition.

Hybrid delivery combines approaches where useful. A new exhibition might require a largely sequential building fit-out while its visitor application evolves through short trials. PRINCE2 can govern each arrangement. Choosing iterative delivery does not remove the need for an investment case, clear authority, acceptable quality or a controlled finish. Choosing linear delivery does not forbid learning or change.

A management stage is a period governed by an authorisation and plan, ending at a point where the board can assess the project and decide on further commitment. A specialist delivery phase or iteration organises how products are created. Their boundaries need not match one for one. Several software iterations can sit within one management stage, and one technical phase can span more than one stage.

Context includes project scale, organisational arrangements, delivery method, commercial relationships and sustainability. Ask about existing policies, supplier contracts, regulatory obligations, team location and access to scarce skills. A contract may impose acceptance milestones, but contractual payment authority and project governance still need to be understood separately. A small budget does not automatically imply low risk or simple stakeholder relationships.

Select controls that fit the uncertainty. Where usability is unclear, an early trial can reduce the risk of building the wrong solution. Where a physical dependency cannot be reversed cheaply, stronger upfront evidence may be necessary. Record assumptions and explain why the chosen arrangements are proportionate. Revisit them when a supplier changes, requirements stabilise or previously hidden constraints become visible.

Delivery and governance

Points to remember

• Iteration refines; increments add usable capability.
• PRINCE2 is compatible with different specialist delivery approaches.
• Consider context before choosing the degree of formality.

Your takeaway

Fit delivery to the product and its uncertainty. Fit management stages to useful control points, while keeping authority and evidence clear across all delivery streams.