Study guide

11.3 Version 1 to Version 2: What Changed and Common Traps

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

11.3 Version 1 to Version 2: What Changed and Common Traps

Key Takeaways Explain This Topic AI

Version 2 was released in May 2025 and aligns PRINCE2 Agile with PRINCE2 Project Management Version 7.

Themes became practices, management products became artifacts, and the Change theme became the Issues practice.

The six-cornered hexagon was replaced by seven performance targets, adding sustainability.

The five targets, five behaviours, Cynefin and the eight guidance points are Version 1 material and are not named in the Version 2 Foundation syllabus.

Version 1 vouchers stopped on 30 June 2026 and the last Version 1 exam date is 31 December 2026.

Last updated: August 2026

11.3 Version 1 to Version 2: What Changed and Common Traps

Quick summary: Version 2 was released in May 2025 and aligns PRINCE2 Agile with PRINCE2 Project Management Version 7 . Vocabulary changed, content was added, and several Version 1 signature concepts left the Foundation syllabus. Because most free material online is still Version 1, cross-contamination is the biggest single risk to your preparation.

The exam itself

  • Version 1 (retired) Version 2 (current)
  • Questions 50 40
  • Pass mark 28 (55%) 24 (60%)
  • Duration 60 minutes 60 minutes
  • Book Closed Closed
  • Certificate validity Lifetime, no renewal 3 years, 20 CPD points
  • Voucher purchase Ended 30 June 2026 Current
  • Final exam date 31 December 2026 —

If a resource says "50 questions, 55% to pass, valid for life", it is describing the retired paper — regardless of what the page title claims. This is the single fastest way to identify stale study material.

Vocabulary changes

  • Version 1 Version 2
  • Themes Practices
  • Change theme Issues practice
  • Management products Artifacts

Principles, themes, processes Principles, people, practices, processes, project context (five integrated elements)

  • Hexagon — six performance aspects Seven performance targets , adding sustainability
  • What Version 2 added
  • Organizational change management — a whole topic within the 30% key-concepts outcome
  • The people integrated element , and with it teams, leadership, culture and communication
  • Being agile vs doing agile as a headline distinction
  • The Agile Onion — processes, practices, principles, values, mindset
  • Agile transformation success factors — agile maturity, psychological safety, agile sustainability
  • Agile scaling as an explicit topic
  • Eleven named roles , including the chief product owner , agile coach , team coach , developer and tester
  • Named agile workshops attached to the processes
  • New artifacts — project canvas, release map, project and team dashboards

The wider context — agile product management, transitioning to operations, continuous agile development and operations

  • AI supporting PRINCE2 Agile
  • Sustainability , as a performance target and as agile sustainability
  • What is no longer in the Foundation syllabus

These are Version 1 signature concepts. They are not named in the Version 2 Foundation syllabus assessment criteria:

The five targets — be on time, protect quality, embrace change, keep teams stable, accept the customer doesn't need everything

  • The five behaviours — transparency, collaboration, rich communication, self-organization, exploration
  • The hexagon as a model, replaced by the seven performance targets
  • The Cynefin framework
  • The eight guidance points

The Version 1 "focus areas" — the Agilometer, requirements, rich communication, frequent releases, contracts — as a grouped topic

Two important qualifications, because "not named in the syllabus" is not the same as "wrong":

The underlying ideas survive. Fixing time and cost while flexing scope is still exactly how PRINCE2 Agile works; it is now expressed through the seven performance targets and their tolerances rather than through a hexagon diagram. Transparency and collaboration are still central; they now appear as characteristics of the agile mindset .

The Agilometer still exists. It appears in the official Version 2 material as a technique within the risk practice for identifying agile adoption issues. What changed is its prominence: it is one technique among many, not the organizing centre of the method.

If a question offers the Agilometer as an option, it is most likely either the correct answer to a risk practice question or a distractor drawn from a neighbouring practice.

The traps that follow

Trap 1 — Answering "50 questions, 55%" logistics questions. Check the version of anything you revise from.

Trap 2 — Saying "theme" when the answer is "practice". And, specifically, looking for a Change practice. It is Issues .

Trap 3 — Naming six performance aspects. There are seven ; the one candidates omit is sustainability .

Trap 4 — Reciting the five behaviours when asked about the agile mindset. The mindset characteristics are empowerment, transparency, adaptability, respect, collaboration, continual learning. Empowerment is the one that promotes autonomy and self-management.

Trap 5 — Confusing "being agile" and "doing agile". Being = mindset. Doing = processes. The exam presents this reversed.

Trap 6 — Confusing the two coaching roles. Agile coach works across teams and the organization; team coach serves one team.

Trap 7 — Confusing the chief product owner with the product owner. CPO is project level and aligns backlogs across teams; PO is team level.

Trap 8 — Confusing team retrospective with project retrospective. Team level every iteration; project level once at closure.

Trap 9 — Attributing priority decisions to a coach. Priority is the product owner's accountability, including when requirements are traded or swapped.

Trap 10 — Treating a stage as an iteration. A stage is a management control period containing releases, each containing iterations.

Trap 11 — Confusing risk with issues. Risk has not happened; an issue has. When a risk materialises, it becomes an issue.

Trap 12 — Ignoring learning outcome 4. Only 5%, but four discrete ideas — agile product management, transition, deployability, AI — that are quick to learn and are absent from every Version 1 resource.