Study guide

4.3 The Seven PRINCE2 Principles

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

4.3 The Seven PRINCE2 Principles

Key Takeaways Explain This Topic AI

The seven principles are: ensure continued business justification, learn from experience, define roles, responsibilities and relationships, manage by stages, manage by exception, focus on products, and tailor to suit the project.

All seven must be applied for a project to be a PRINCE2 project; they are universal, self-validating and empowering.

'Ensure continued business justification' is the principle that explains whether a project can still deliver value.

'Define roles, responsibilities and relationships' was extended in PRINCE2 7 to include relationships, not just roles and responsibilities.

'Manage by exception' is what makes delegated, self-managing agile delivery compatible with project board control.

Last updated: August 2026

4.3 The Seven PRINCE2 Principles

Quick summary: Seven principles. All must be applied — dropping one means the project is not a PRINCE2 project. They are universal (they apply to every project), self-validating (proven in practice over decades) and empowering (they give practitioners confidence and the ability to shape their approach).

The seven principles

# Principle What it requires

1 Ensure continued business justification There is a justifiable reason to start, and it remains valid and is re-tested throughout

2 Learn from experience Lessons are sought at the start, captured during, and passed on at the end

3 Define roles, responsibilities and relationships An agreed structure that engages business, user and supplier interests, and defines how those roles relate

4 Manage by stages Plan, monitor and control the project stage by stage, with a board decision at each boundary

5 Manage by exception Define tolerances for each performance target, delegate authority within them, escalate only when they will be breached

6 Focus on products Define and agree the products and their quality criteria before deciding how to produce them

7 Tailor to suit the project Scale the method to the project's context, size, complexity, importance, team capability and risk

Two wording points that matter in Version 7 and therefore in PRINCE2 Agile Version 2:

Principle 3 was formerly "defined roles and responsibilities" . It now explicitly includes relationships , reflecting the elevation of the people element — how roles interact matters as much as who holds them.

Principle 7 was formerly "tailor to suit the project environment" . It is now "tailor to suit the project" .

  • Taking them one at a time
  • 1. Ensure continued business justification

There must be a justifiable reason to start the project, that justification must remain valid throughout, and it must be documented and approved . If it ceases to be valid, the project should be stopped — a project that is stopped early for good reason is a success, not a failure.

This is the principle that answers the question "can this project still deliver value?" It is the direct parent of the business case practice and of the project board's decision at every stage boundary.

In agile delivery this principle becomes sharper rather than weaker. Frequent releases produce real evidence about whether the forecast benefits are materialising, so continued justification can be tested against measured outcomes rather than against a spreadsheet written a year earlier.

2. Learn from experience

Lessons are actively sought when the project starts, recorded as it runs, and passed on when it closes. The intent is that lessons change behaviour , not merely that they are logged.

Agile delivery is unusually well suited to this because the retrospective is a scheduled, recurring mechanism for it. The team retrospective workshop improves the team's next iteration; the project retrospective feeds the organization's next project.

3. Define roles, responsibilities and relationships

A project needs an explicit organization structure engaging the three project interests — business, user and supplier — with clear accountability and clear relationships between the roles.

Agile does not dissolve this. Adding a product owner and a team coach does not remove the need to know who is accountable for the business case. Chapter 9 covers the eleven roles the Version 2 syllabus names.

4. Manage by stages

The project is planned, monitored and controlled stage by stage. A stage boundary is a genuine decision point: the board reviews what has been delivered and the updated business case, and authorizes the next stage or stops the project.

A stage is not an iteration. A stage exists for management control and may contain several releases, each containing several iterations.

5. Manage by exception

Tolerances are defined for each performance target at each level of the project. Within its tolerances, a level has delegated authority to act without referring upward . Only a forecast breach is escalated.

This is the principle that makes agile delegation and project governance compatible. Self-managing teams need genuine autonomy; project boards need genuine control. Manage by exception delivers both by making the boundary explicit: the team decides everything inside the tolerance, the board decides everything outside it. Without it, either the board micromanages or it loses control.

6. Focus on products

PRINCE2 is product-based. You define what is to be delivered and its quality criteria first, and derive the activities from that — not the other way round.

The agile expression of this is precise product definition through user stories, acceptance criteria and the Definition of Done. Note the compatibility: a backlog is a product-focused artifact. It lists things to be delivered, not tasks to be performed.

7. Tailor to suit the project

PRINCE2 is scaled to the project's context, size, complexity, importance, team capability and risk. Tailoring decisions are recorded — typically at initiation — so that they are deliberate and visible rather than drift.

Tailoring is what PRINCE2 Agile is . But note the limit: you tailor the practices, the processes and the artifacts. You never tailor away a principle. A project that has abandoned continued business justification has not tailored PRINCE2; it has stopped using it.