Study guide
9.1 Directing and Managing Roles
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.1 Directing and Managing Roles
Key Takeaways Explain This Topic AI
The Version 2 syllabus names eleven PRINCE2 Agile roles, of which six operate at the directing and managing levels.
The project executive owns the business case and is accountable for value for money and for the project's continued justification.
The chief product owner works at project level and ensures that the project backlog and the delivery teams' product backlogs align.
Project assurance provides independent assurance to the project board that governance checks are properly applied.
Project support reports directly to the project manager and maintains information held on project dashboards.
Last updated: August 2026
9.1 Directing and Managing Roles
Quick summary: The syllabus names eleven PRINCE2 Agile roles . Six sit at the directing and managing levels: project executive, chief product owner, senior supplier, project assurance, project manager, project support . The other five are delivery roles, covered in section 9.2. Expect questions that test the boundary between two adjacent roles.
The eleven roles at a glance
- Level Roles
- Directing Project executive · Chief product owner · Senior supplier · Project assurance
- Managing Agile coach · Project manager · Project support
- Delivering Product owner · Team coach · Developer · Tester
The agile coach and the delivery roles are covered in section 9.2.
Project executive
Accountable for the project as a whole. The executive owns the business case and is accountable for value for money — that the project remains desirable, viable and achievable and delivers a return that justifies the investment.
Specific responsibilities:
- Owns and approves the business case; ensures it is re-tested at each stage boundary
- Chairs the project board and holds the casting decision
- Secures funding and authorizes the project, each stage, and closure
- Sets project-level tolerances and decides on exceptions escalated by the project manager
- Appoints the project manager and the other board roles
- Balances the demands of the business, user and supplier interests
The executive represents the business interest . There is only ever one executive — accountability cannot be shared without becoming nobody's.
Chief product owner
The chief product owner (CPO) is the project-level product ownership role, and it is a Version 2 addition that does not exist in older PRINCE2 Agile material.
The defining responsibility: ensuring that the project backlog and the delivery teams' product backlogs align. Where several teams contribute to one product, each has its own delivery backlog. Without a single role holding project-level ordering, the teams optimize locally and the project loses coherence — five teams each building their own highest-priority item, none of which combine into a releasable increment.
Specific responsibilities:
- Owns and orders the project backlog , expressing requirements at project level
- Ensures delivery teams' product backlogs are aligned with it
Represents the user and product interest at the directing level, working to the benefit objectives the business case sets out
- Makes cross-team priority decisions and resolves conflicts between teams' competing needs
- Works with the release map so that each release is a coherent, releasable whole
The boundary to hold: the CPO works at project level ; the product owner (section 9.2) works with a single delivery team . On a small single-team project the two may be combined; on a multi-team project they must not be.
Senior supplier
Represents the supplier interest : those designing, developing, procuring, implementing and, where relevant, operating and maintaining the product.
Responsibilities:
Confirms that the products can be delivered within the agreed cost and timescale — the achievable half of the business case test
- Commits supplier resources to the project
- Ensures the supplier's quality procedures and standards are applied
- Represents supplier interests in board decisions and exception handling
On a commercial project the senior supplier sits in the supplying organization, which makes the customer/supplier boundary an explicit part of the organization practice.
Project assurance
Provides the project board with independent assurance that the project is being conducted properly. It is a board responsibility, and the board may perform it directly or delegate it — but never to the project manager , because assurance must be independent of the role it assures.
Assurance follows the three interests:
- Assurance strand Assures On behalf of
- Business assurance Value for money, business case integrity Executive
- User assurance The product will meet user needs and realize benefits Chief product owner / user interest
- Supplier assurance Products are technically sound and standards are applied Senior supplier
In an agile context project assurance is the role that ensures product delivery includes governance checks — that the Definition of Done actually reflects the required standards, that quality activities are genuinely performed, and that reported progress corresponds to product that exists.
Project manager
Responsible for the day-to-day management of the project on behalf of the board, within the tolerances the board has set.
Responsibilities:
- Plans stages and manages delivery against them
- Agrees work packages with delivery teams, including tolerances and the Definition of Done
Monitors progress, produces highlight reports, and raises exception reports when a tolerance is forecast to be breached
- Manages risks and issues, escalating those beyond delegated authority
- Maintains the business case on the executive's behalf
- Manages the interfaces between teams, suppliers and the wider organization
In a PRINCE2 Agile project the project manager's style shifts markedly. They manage work packages and tolerances , not individuals' daily tasks — the delivery team is self-managing within its work package. The relationship is one of servant leadership : removing impediments, providing context and shielding the team, rather than directing its work.
Project support
An administrative and information-management function, and — importantly for the exam — project support reports directly to the project manager .
Responsibilities:
- Administers the project's information: registers, logs, plans and reports
- Maintains the information held on project dashboards
- Manages configuration and version control of products
- Administers tooling and provides planning support
- Arranges and services workshops and board meetings
Where a project management office exists, it commonly provides project support. It is a support function, not a governance one: project support maintains the dashboard, but project assurance is what independently confirms the dashboard tells the truth.
The boundaries most often confused
- Confusion The distinction
- Executive vs project manager Executive owns the business case; project manager maintains it
- Chief product owner vs product owner CPO works at project level across teams; PO works with a single team
Project assurance vs project support Assurance is independent oversight for the board; support is administration for the project manager
Project assurance vs project manager Assurance must be independent, so it can never be delegated to the project manager
Senior supplier vs delivery team Senior supplier commits resources and confirms achievability at board level; the team builds