Managing Product Delivery (MP) is the PRINCE2 process where the actual work of creating products happens, and it is the natural home for agile ways of working like Scrum and Kanban. In this process, the Team Manager and delivery team accept, execute, and deliver Work Packages authorised by the Proj…Managing Product Delivery (MP) is the PRINCE2 process where the actual work of creating products happens, and it is the natural home for agile ways of working like Scrum and Kanban. In this process, the Team Manager and delivery team accept, execute, and deliver Work Packages authorised by the Project Manager, and this is where agile delivery frameworks integrate seamlessly with PRINCE2's controlled environment. Scrum fits into MP by structuring work into fixed-length timeboxes called sprints, typically two to four weeks. The team pulls Product Backlog items into a Sprint Backlog during sprint planning, conducts daily stand-ups to synchronise progress, and delivers a potentially shippable increment at each sprint's end. Scrum events such as sprint reviews and retrospectives support inspection and adaptation, while roles like Product Owner and Scrum Master complement PRINCE2 roles. The Work Package in PRINCE2 maps well to a set of sprints or a release, providing boundaries and tolerances within which the self-organising team operates. Kanban, by contrast, focuses on visualising workflow using a Kanban board, limiting work in progress (WIP), and managing continuous flow rather than fixed timeboxes. It emphasises pulling work as capacity allows, reducing bottlenecks, and improving cycle time. Kanban suits environments where priorities change frequently or where a steady, continuous delivery stream is preferred over batch releases. Within MP, both approaches respect PRINCE2 controls: reporting through Checkpoint Reports, managing quality via the Quality Register, and escalating when tolerances are threatened. PRINCE2 Agile encourages tailoring, so teams may blend Scrum and Kanban (Scrumban) or use whichever best fits the context. Agile workshops, such as planning sessions, reviews, and retrospectives, provide collaborative forums for these activities. Ultimately, MP with Scrum or Kanban balances agile flexibility, empowerment, and frequent delivery with PRINCE2's governance, ensuring value is delivered incrementally while maintaining overall project direction and control.
Managing Product Delivery with Scrum and Kanban
Managing Product Delivery with Scrum and Kanban
In PRINCE2 Agile, the Managing Product Delivery (MP) process is the point where the disciplined governance of PRINCE2 meets the working practices of agile frameworks such as Scrum and Kanban. Understanding how these approaches integrate is a key topic for the PRINCE2 Agile Foundation exam.
Why It Is Important
The Managing Product Delivery process is where the actual product work gets done. It sits at the boundary between the Team Manager (or delivery team) and the Project Manager. In an agile context, this is the process most naturally aligned with agile ways of working, because it deals directly with creating and delivering products.
Understanding this integration is important because:
It shows how PRINCE2 governance (Work Packages, quality criteria, reporting) coexists with agile self-organisation and delivery. It ensures teams deliver value frequently and predictably while remaining within agreed tolerances. It bridges the gap between management-level control and team-level delivery.
What It Is
The Managing Product Delivery process has three core activities:
1. Accept a Work Package - the team agrees what needs to be delivered. 2. Execute a Work Package - the team builds and tests the products. 3. Deliver a Work Package - the team hands over completed, quality-checked products.
In PRINCE2 Agile, the delivery of the Work Package is achieved using agile methods. Two of the most common are:
Scrum - an iterative, timeboxed framework built around fixed-length sprints. It uses defined roles (Product Owner, Scrum Master, Development Team), events (Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective) and artefacts (Product Backlog, Sprint Backlog, Increment).
Kanban - a flow-based method focused on visualising work, limiting work in progress (WIP), and managing continuous delivery. It uses a Kanban board with columns representing workflow stages and emphasises pull-based work rather than fixed timeboxes.
How It Works Together
A Work Package in PRINCE2 acts as the container of authority and constraints. Within that Work Package, the team uses Scrum or Kanban to organise and deliver the work:
A Work Package might map to one or more sprints in Scrum, or a stream of continuous flow in Kanban. The Team Manager role may be fulfilled or shared by agile roles such as the Scrum Master or Product Owner. Progress is tracked using agile tools like burn-down/burn-up charts or cumulative flow diagrams, feeding into PRINCE2 Checkpoint Reports. Quality is assured through agile practices such as the Definition of Done, acceptance criteria, and frequent testing.
Scrum tends to suit projects where requirements can be batched into iterations, while Kanban suits environments with continuous, variable flow or maintenance-style work. PRINCE2 Agile is deliberately tool-agnostic, allowing teams to choose the most appropriate approach.
Key Concepts to Remember
Timeboxing: Scrum sprints are fixed in length; scope may flex but time does not. WIP limits: Kanban restricts the amount of work in progress to improve flow. Servant leadership: The Scrum Master facilitates rather than commands. Prioritisation: Techniques such as MoSCoW help decide what is delivered within tolerance. Frequent delivery: Both methods emphasise delivering working products regularly.
Exam Tips: Answering Questions on Managing Product Delivery with Scrum and Kanban
1. Know the mapping. Be clear that Managing Product Delivery is the PRINCE2 process most associated with agile delivery, and that Scrum/Kanban operate within Work Packages.
2. Distinguish Scrum from Kanban. Exam questions often test whether you can identify which method uses timeboxes (Scrum) versus WIP limits and continuous flow (Kanban).
3. Match roles and events. Remember Scrum roles (Product Owner, Scrum Master, Development Team) and events. Kanban has no prescribed roles or events - do not attribute Scrum events to Kanban.
4. Watch for 'select the best method' questions. Choose Kanban for continuous flow/variable work and Scrum for iterative, batched requirements.
5. Link to PRINCE2 governance. When asked how control is maintained, connect agile reporting (burn-down charts, cumulative flow) to Checkpoint Reports and tolerances.
6. Beware of distractors. Foundation questions may include plausible but incorrect terms. Read carefully and eliminate options that mix frameworks incorrectly.
7. Remember PRINCE2 Agile is tool-neutral. The framework blends with agile rather than replacing it - answers implying PRINCE2 discards its structure are usually wrong.
By understanding how Scrum and Kanban fit inside the Managing Product Delivery process, you will be able to confidently answer both knowledge-based and scenario-based questions in the exam.
