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

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

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

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":

1. 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.
2. 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.