Study guide
10.6 Managing Product Delivery and Its Agile Workshops
PRINCE2 Agile Foundation Version 2
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: The Version 2 Exam & PRINCE2 Agile Essentials
1.1 About the PRINCE2 Agile Foundation (Version 2) Exam 1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile 1.3 PRINCE2 Agile Key Terms You Must Be Able to Define
2 Chapter 2: Agile and the Agile Mindset
2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU 2.2 Being Agile vs Doing Agile, and the Benefits of Both 2.3 The Agile Mindset and the Agile Onion 2.4 The Agile Manifesto and Popular Agile Approaches
3 Chapter 3: Key Agile Concepts and Techniques
3.1 User Stories, Agile Estimation, and the Definitions of Ready and Done 3.2 MVP, Burn Charts, Workshops and Agile Events
4 Chapter 4: PRINCE2 Project Management Foundations
4.1 Projects, Project Management and the Seven Performance Targets 4.2 Project Contexts and the Five Integrated Elements 4.3 The Seven PRINCE2 Principles 4.4 Agile Scaling and Agile Transformation Success Factors
5 Chapter 5: People and Organizational Change Management
5.1 Organizational Change Management: Definition, Stakeholders and Culture 5.2 How Agile Supports Change Management and How PRINCE2 Addresses People 5.3 Project Teams, Leading Effective Teams and Communication
6 Chapter 6: PRINCE2 Agile Essentials — Principles and Practices
6.1 How the PRINCE2 Principles Support the Agile Context 6.2 The Purpose of the Seven PRINCE2 Agile Practices
7 Chapter 7: The Practices (Part 1) — Business Case, Organization, Plans
7.1 The Business Case Practice in an Agile Context 7.2 The Organization Practice in an Agile Context 7.3 The Plans Practice in an Agile Context 7.4 Plans Artifacts and Techniques: Release Maps, Timeboxes and Estimation
8 Chapter 8: The Practices (Part 2) — Quality, Risk, Issues, Progress
8.1 The Quality Practice in an Agile Context 8.2 Quality Artifacts and Techniques: Ready, Done and Continuous Testing 8.3 The Risk Practice in an Agile Context 8.4 The Issues Practice in an Agile Context 8.5 The Progress Practice in an Agile Context 8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards
9 Chapter 9: The Eleven PRINCE2 Agile Roles
9.1 Directing and Managing Roles 9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester
10 Chapter 10: The Processes and Their Agile Workshops
10.1 The Purpose of the Seven PRINCE2 Agile Processes 10.2 Starting up a Project and Its Agile Workshops 10.3 Directing a Project and Its Agile Workshops 10.4 Initiating a Project and Its Agile Workshops 10.5 Controlling a Stage and Its Agile Workshops 10.6 Managing Product Delivery and Its Agile Workshops 10.7 Managing a Stage Boundary and Its Agile Workshops 10.8 Closing a Project and Its Agile Workshops
11 Chapter 11: The Wider Context, AI, and Exam Preparation
11.1 PRINCE2 Agile Beyond the Project Environment 11.2 How AI Can Support PRINCE2 Agile 11.3 Version 1 to Version 2: What Changed and Common Traps 11.4 Final Review and Exam-Day Strategy
10.6 Managing Product Delivery and Its Agile Workshops
Key Takeaways Explain This Topic AI
Managing product delivery controls the link between the project manager and the delivery team through work packages.
Its three activities are accept a work package, execute a work package, and deliver a work package.
The team planning workshop plans the team's timebox, and team OKRs are defined there.
In the team retrospective workshop the team shares the key accomplishments of its iteration and agrees improvements.
This is where agile is most concentrated: iterations, backlogs, self-management and continuous testing all live at this level.
Last updated: August 2026
10.6 Managing Product Delivery and Its Agile Workshops
Quick summary: MP controls the link between the project manager and the delivery team through work packages. Its three activities are accept , execute and deliver a work package. Its agile workshops include the team planning workshop , where team OKRs are defined , and the team retrospective workshop , where the team shares the key accomplishments of its iteration .
Purpose
The purpose of managing product delivery is to control the link between the project manager and the delivery team, by placing formal requirements on accepting, executing and delivering project work.
MP runs in parallel with controlling a stage : CS at the managing level, MP at the delivering level. They are the two halves of the same conversation, and the work package is the interface between them.
- The three activities
- Accept a work package
The team and the project manager agree what will be produced. The team confirms it understands the products, the acceptance criteria, the Definition of Done , the tolerances and the reporting arrangements — and confirms it can deliver within them.
This is a genuine negotiation, not a hand-down. A team that accepts a work package it does not believe it can meet has already guaranteed an exception later.
Execute a work package
The team does the work — iteration by iteration:
- Pull ready items from the delivery backlog into the timebox
- Build and test within the iteration , not afterwards
- Hold planning, review and retrospective events
- Keep the team dashboard current so status is visible without being requested
- Raise impediments, risks and issues promptly
- Self-manage : decide how the work is done, sequence it, swarm on blockers
The project manager stays out of the how. Their involvement is limited to tolerances, impediments the team cannot remove, and interfaces with other teams.
Deliver a work package
The team confirms the products are complete — meeting their acceptance criteria and the Definition of Done — and hands them back for the project manager to receive in CS.
The work package as governance interface
- Above the line — project manager Below the line — delivery team
- What products, to what criteria How they will be built
- Tolerances the team works within Sequencing and technical approach
- Definition of Done Who does what
- Reporting arrangements Iteration length and internal cadence
- Interfaces and dependencies Estimating approach
A work package that specifies how the team should build something has crossed the line and removed the self-management the delivery approach depends on. Getting this boundary right is most of what makes a PRINCE2 Agile project work.
The team planning workshop
The team planning workshop plans the team's timebox. It:
- Reviews the prioritized items at the top of the delivery backlog
- Confirms items meet the Definition of Ready
- Sizes the work against the team's capacity, using velocity where history exists
- Agrees the goal for the timebox
Defines the team's OKRs — the objectives and key results that express what the team is aiming to achieve and how it will know
The OKR point is directly examinable : team OKRs are defined in the team planning workshop, not in release planning, progress review or project closure.
The team retrospective workshop
The team retrospective workshop is where the team inspects how it worked and agrees improvements. It is also where the team shares the key accomplishments of its iteration — an explicitly named feature of this workshop.
Naming accomplishments is not decoration. A retrospective that only lists problems steadily erodes morale and psychological safety; one that starts from what went well establishes the safety needed for the harder conversation about what did not.
A typical structure: set the scene, review what happened, name the key accomplishments, identify what hindered the team, agree a small number of improvement actions the team itself owns, and check the previous iteration's actions were actually done.
Two conditions determine whether it is worth holding:
Psychological safety. Without it, nobody names the real problem.
Authority to act. Improvement actions the team cannot implement produce cynicism rather than improvement.
Distinguish the team retrospective workshop (team level, every iteration, this team's way of working) from the project retrospective (project level, at closure, lessons for the organization).
Agile tailoring of MP
Checkpoint reports are often replaced entirely by a live team dashboard.
The team decides its own iteration length , within the work package's constraints.
Testing is inside the team , which is why tester is a named delivery role.
The product owner accepts items continuously , rather than everything being accepted at work package hand-back.
Tolerances are set on the work package , so the team knows exactly where its authority ends.