Study guide
1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile
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
1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile
Key Takeaways Explain This Topic AI
PRINCE2 Agile is not a delivery method — it is guidance on how to configure and tailor PRINCE2 Project Management so that it works with agile ways of working such as Scrum, Kanban, Lean and Lean Startup.
The blend is deliberately asymmetric: PRINCE2 contributes direction and management, and agile contributes the delivery layer.
The most commonly cited challenge in merging project management and agile is the absence of a common language or shared terminology between the two communities.
PRINCE2 Agile keeps all seven PRINCE2 processes, all seven practices and all seven principles intact — nothing is added, removed, merged or split.
Blending works at three levels: project direction, project management, and product delivery.
Last updated: August 2026
1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile
Quick summary: PRINCE2 Agile describes how to configure and tailor PRINCE2 Project Management so it can be used effectively alongside agile behaviours, concepts, frameworks and techniques. It does not supply a delivery method of its own. PRINCE2 owns direction and management; an agile approach such as Scrum or Kanban owns delivery.
What PRINCE2 Agile is — and is not
The single most common misconception at Foundation level is that PRINCE2 Agile is "the agile version of PRINCE2", a separate method you adopt instead of PRINCE2. It is not.
PRINCE2 Agile is guidance for tailoring. It takes the PRINCE2 method — seven principles, the people element, seven practices, seven processes, and the project context — and explains how each of them should be configured when the delivery teams are working iteratively and incrementally.
Three things follow from that definition, and each is examinable:
PRINCE2 Agile adds no new processes and removes none. The same seven processes run: starting up a project, directing a project, initiating a project, controlling a stage, managing product delivery, managing a stage boundary, and closing a project. What changes is how each is carried out, and which agile workshops support it.
PRINCE2 Agile does not tell you which agile approach to use. It is compatible with Scrum, Kanban, Lean, Lean Startup and hybrids of them. Choosing among them is a tailoring decision driven by the project's context.
PRINCE2 Agile assumes no prior agile capability. Part of its value is helping an organization that already governs by PRINCE2 to introduce agile delivery without abandoning governance.
The three levels of a project
PRINCE2 organizes a project into levels of responsibility, and the blend of PRINCE2 and agile is different at each one. This is the mental model to carry into the exam.
Level Who works here What PRINCE2 contributes What agile contributes
Project direction Project board (executive, senior user, senior supplier) Governance, authorization, business justification, tolerances, manage by exception Faster feedback on value, willingness to re-prioritize between releases
Project management Project manager, project support, project assurance Stages, plans, reporting, risk and issue handling, work packages Release maps, dashboards, workshops, flexing scope against fixed timeboxes
Product delivery Delivery teams — product owner, team coach, developers, testers Work packages, product descriptions, tolerances handed down Iterations, backlogs, user stories, Definition of Done, retrospectives, self-management
The weight of agile increases as you move down the table. At the direction level, the project board still directs by exception and still asks whether the project remains desirable, viable and achievable. At the delivery level, the team is genuinely self-managing. The project management level is where the translation happens — and it is where the project manager earns their keep.
Why blending is hard: the common-language problem
If the exam asks what is often seen as a challenge when merging project management and agile , the answer is not "agile has no reporting mechanisms" or "agile has no tracking metrics". Both of those are false: agile has burn charts, dashboards, velocity and cumulative flow.
The classic challenge is having no common language or terminology across the organization.
This matters because the same word means different things on either side of the divide:
A stage in PRINCE2 is a management control point. A sprint or iteration in Scrum is a delivery timebox. A stage typically contains one or more releases, and each release contains one or more iterations. They are not synonyms.
Scope in a plan-driven contract means "everything specified". In agile, scope is the variable that flexes so that the deadline holds.
Done to a project board can mean "handed over"; to a delivery team it means "meets the Definition of Done".
When the two communities use the same words for different concepts, governance conversations degrade into mutual suspicion: the board thinks the team is refusing to commit, the team thinks the board is micromanaging. PRINCE2 Agile addresses this head-on by supplying a shared glossary and by defining artifacts — the project canvas, the release map, dashboards, backlogs — that both sides read the same way.
Other real frictions the guidance acknowledges:
Different attitudes to documentation. PRINCE2 asks what information is needed and who needs it; agile asks whether the document earns its cost. Tailoring resolves this by right-sizing the artifact, not by deleting it.
Different attitudes to commitment. Fixed-scope commitment versus fixed-date commitment with flexible scope.
Different governance rhythms. Stage boundaries every few months versus iteration reviews every one or two weeks.
What "blending" looks like in practice
Blending is not a single decision made once at initiation. It runs throughout:
At initiation , agree how agile will be used and record it — including which approach, how tolerances will be set, how progress will be reported, and what the Definition of Done is.
During delivery , keep the governance artifacts alive and lightweight: a dashboard the board can read, a release map that shows when features land, a backlog that is genuinely prioritized.
At each stage boundary , re-test continued business justification against what has actually been delivered rather than against what was forecast.
The test of a good blend is simple: the project board can answer "is this still worth doing?" from evidence produced as a by-product of the delivery team's normal working, not from a report written specially for them.