Study guide

7.2 The Organization Practice in an Agile Context

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

7.2 The Organization Practice in an Agile Context

Key Takeaways Explain This Topic AI

The organization practice defines the project's responsibilities and establishes its structure of accountability.

The three project interests — business, user and supplier — must all be represented on the project board, whatever agile roles are added.

Agile roles are integrated with PRINCE2 roles rather than replacing them; the mapping must be agreed explicitly at initiation.

Project support reports directly to the project manager, while delivery team members work within a self-managing team.

Techniques in this practice include personas, team skill matrices, delegation matrices, delegation poker and servant leadership.

Last updated: August 2026

7.2 The Organization Practice in an Agile Context

Quick summary: The organization practice defines the project's responsibilities . It establishes the three project interests, the four levels of management, and — in an agile context — how PRINCE2 roles and agile delivery roles fit together without duplicating authority .

Purpose

The organization practice defines and establishes the project's structure of accountability and responsibilities: who is accountable for what, who reports to whom, and how the roles relate to one another. It is the practice that gives the define roles, responsibilities and relationships principle its machinery.

The three project interests

Every project must represent three interests, and the project board exists to hold them:

  • Interest Question it protects Held by
  • Business Is this value for money? Is it still justified? Executive
  • User Will the product be usable, and will the benefits be realized? Senior user
  • Supplier Can we actually build and support this? Senior supplier

Adding agile roles does not remove any of these. A team-level product owner is not a substitute for project-level user representation , and a delivery team is not a substitute for a senior supplier. If a project has a product owner and nobody holding the user interest at the directing level, that interest is being represented by someone whose accountability is backlog ordering — which is not the same thing as accountability for benefit realization.

Where the chief product owner fits. The eleven roles named in the Version 2 syllabus include the chief product owner rather than listing a senior user separately. On a PRINCE2 Agile project the chief product owner is the role that carries the user and product interest at the directing level , owning the project backlog and working to the benefit objectives the business case sets out. Where an organization also appoints a senior user in the PRINCE2 Project Management sense, the two work as a pair — the senior user accountable for specifying and realizing benefits, the chief product owner translating those objectives into project-level backlog priority. What must never happen is for neither to exist, leaving the user interest to a team-level product owner.

The four levels of management

Level Who Responsibility

Corporate, programme management or the customer Outside the project Commissions the project, sets its objectives and constraints, receives its benefits

  • Directing Project board Authorizes, sets tolerances, directs by exception, decides at stage boundaries
  • Managing Project manager Day-to-day management of the stage within tolerances

Delivering Team manager, product owner, team coach, delivery team Produces the products within work package tolerances

The directing level delegates day-to-day management to the managing level — that delegation happens in the directing a project process, and it is what makes manage by exception operable.

Reporting relationships

Two relationships are examinable and frequently confused:

Project support reports directly to the project manager. Project support is a project management function — administration, tooling, configuration and information management — and it sits under the project manager.

Delivery team members do not report to the project manager. They work within a self-managing delivery team. The project manager agrees work packages with the team, sets tolerances, and then stays out of the how. The team coach serves the team rather than managing it, and the product owner owns priority rather than people.

That distinction is exactly what makes agile delivery work inside PRINCE2 governance: the project manager manages work packages and tolerances , not individuals' daily tasks.

Integrating agile and PRINCE2 roles

The practical work of this practice on a PRINCE2 Agile project is mapping. Common integrations:

PRINCE2 role Common agile counterpart How they relate

Senior user Chief product owner (project level) The chief product owner carries the user and product interest at the directing level and owns the project backlog

Senior user Product owner (team level) The product owner works to the agreed benefit objectives and orders one team's backlog accordingly

Team manager Product owner or team coach Depending on the team's shape, one of them fulfils the work-package accountability

  • Project manager — (retained) Manages across teams, stages, tolerances and the board relationship
  • — Chief product owner Where multiple teams contribute, aligns the project backlog with delivery backlogs
  • — Agile coach / team coach Builds capability and removes impediments; not a line manager

The mapping must be agreed and recorded at initiation . The failure mode is ambiguity: a senior user and a product owner both believing they set priority, or a project manager and a team coach both believing they resolve impediments. Chapter 9 covers all eleven roles the syllabus names.

Artifacts and techniques

Artifacts in this practice include role descriptions, the project's organization structure, the communication management approach, and — in an agile context — the team dashboard and the working agreements a team produces in its kickoff workshop.

Techniques the syllabus associates with organizing an agile project:

Personas — defining and prioritizing user groups, so that "the user" is a specific, understood set of people rather than an abstraction. The project canvas workshop is where this typically happens.

Team skill matrix — a grid of people against skills that exposes single points of failure and drives cross-skilling.

Delegation matrix — an explicit statement of which decisions the team takes alone, which after consultation, and which are escalated.

Delegation poker — a collaborative technique for agreeing those delegation levels, which surfaces mismatches between the autonomy a manager thinks they granted and the autonomy the team believes it has.

Servant leadership — putting team members' needs above your own; the leadership style appropriate to coaching roles and to the project manager's relationship with delivery teams.

Working agreements and team norms — how the team agrees to operate, established in the kickoff workshop.

Tailoring the organization practice

Small projects combine roles. The executive may also be the senior user; the project manager may also be the team manager. What cannot be combined is anything that removes a project interest or creates a conflict — the executive should not also be the senior supplier, because value for money and supplier margin pull in opposite directions.

Multi-team projects add a chief product owner and require explicit cross-team decision rights.

Commercial projects need the customer/supplier boundary made explicit in role descriptions, because accountability crosses an organizational boundary.

Loading diagram... Four levels of management and where agile roles sit