Study guide
9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester
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
9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester
Key Takeaways Explain This Topic AI
The agile coach works across the organization to build agile capability; the team coach serves a single delivery team.
The product owner owns and orders one team's product backlog and is consulted to agree priority when requirements are traded or swapped.
Developers build the product; testers verify it — and testing sits inside the iteration rather than in a downstream phase.
Delivery team members do not report to the project manager; they work within a self-managing team.
Coaching roles lead by serving: they remove impediments and build capability rather than directing the work or setting priority.
Last updated: August 2026
9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester
Quick summary: Agile coach builds agile capability across the organization; team coach serves one delivery team; product owner owns and orders one team's backlog and agrees priority when requirements are traded; developers build and testers verify, both within the iteration. None of them reports to the project manager in a line-management sense.
Agile coach
The agile coach builds agile capability, typically working across several teams or across the organization rather than being embedded in one.
Responsibilities:
Coaches teams on agile best practices — this phrasing identifies the role in an exam question
Builds capability so that agile ways of working survive the coach's departure, which is what agile sustainability requires
Supports the shift from doing agile to being agile , working at the values and mindset layers of the Agile Onion
- Advises leadership on removing organizational impediments to agility
- Helps assess and raise agile maturity , and works to establish psychological safety
The agile coach has no authority over the work . They influence and develop; they do not direct, and they do not set priority.
Team coach
The team coach serves a single delivery team . Where the agile coach works broadly, the team coach works deeply with one team.
Responsibilities:
- Facilitates the team's events: planning, reviews, and the team retrospective workshop
- Removes impediments — the classic servant-leadership act
- Protects the team from interruption and from unreasonable outside demands
- Helps the team improve how it works, iteration by iteration
- Supports the team's self-management rather than substituting for it
The team coach is closest to the Scrum master accountability. Two things they are not : they are not the team's line manager, and they do not decide priority — that is the product owner's.
Telling the coaches apart
- Agile coach Team coach
- Scope Multiple teams, or the organization One delivery team
- Focus Capability, maturity, culture This team's effectiveness now
Typical act Coaching teams on agile best practices; advising leadership Facilitating events; removing this team's impediments
- Authority None over the work None over the work
- Product owner
The product owner (PO) owns and orders one delivery team's product backlog , and is the single point of accountability for what that team builds next.
Responsibilities:
- Owns and orders the team's product backlog by value
- Refines items with the team, ensuring they meet the Definition of Ready
- Defines acceptance criteria and accepts or rejects completed items
Is consulted to assess and agree the priority of tasks when requirements are traded or swapped — priority is their accountability
Represents user needs day to day, working within the benefit objectives the business case sets and the ordering the chief product owner has established at project level
Is available to the team continuously; an absent product owner is one of the commonest causes of stalled iterations
Boundaries: the product owner does not own the business case — the executive does. And on a multi-team project the product owner works within the project-level ordering set by the chief product owner .
Developer
Developers build the product. The term covers everyone doing the work of creating the increment — not only software engineers, but analysts, designers, engineers and any specialists the domain requires.
Responsibilities:
- Build the products described in the work package to the agreed quality criteria
- Estimate the work, using relative estimation
- Participate in planning, reviews and retrospectives
- Adhere to the Definition of Done
Self-manage: decide how the work is done, sequence it, and collaborate to finish it — including swarming on a single item when that gets it delivered sooner
Raise impediments, risks and issues promptly
Developers work within a self-managing team and do not report to the project manager . The project manager agrees the work package and its tolerances; the team decides how to meet it.
Tester
Testers verify that the product meets its acceptance criteria and its quality criteria. That testing is named as a distinct role in the Version 2 syllabus reflects how much this matters in an agile context.
Responsibilities:
- Design and run tests against acceptance criteria and quality criteria
- Test within the iteration , alongside development, rather than in a downstream phase
Build and maintain automated tests, which is what makes a demanding Definition of Done affordable to enforce every iteration
Contribute to the Definition of Ready and the Definition of Done
Work with the product owner on behaviour-driven development examples, turning acceptance criteria into executable tests
Surface quality risks and technical debt early
The key structural point: testing is inside the team and inside the iteration. A separate downstream testing department makes it impossible to complete an item within a timebox, which makes the Definition of Done unachievable and turns "done" into a claim rather than a fact.
How the delivery roles fit together
- Question Role
- What should we build next? Product owner (within the chief product owner's project-level ordering)
- How will we build it? The developers and testers, self-managing
- Who removes what is blocking us? Team coach
- How do we get better at working this way? Agile coach, and the team's own retrospectives
- Is it acceptable ? Product owner, against acceptance criteria and the Definition of Done
That table is the cleanest defence against the commonest exam error in this area: attributing priority decisions to a coach, or attributing impediment removal to the product owner.