ASSURANCE DNA · PROJECT GOVERNANCE METHOD

PRINCE2

A tailorable project-management method built around continued business justification, defined organisation, product focus, stage control, exception and learning.

Who can decide, within what tolerance, and when must the project escalate rather than drift?
REFERENCEPRINCE2 Project Management (Version 7), official materials v7.2CURRENT STATE · 26 JUL 2026Version 7 is the current PeopleCert method family; certification naming and official assets were updated in January 2026.BID ENTRYQualify · Model · Story · Comply · Review · Mobilise · Measure

PRINCE2 is a governance method, not a complete delivery toolkit or guarantee of on-time delivery. It must be tailored without removing its control logic. Source-bounded interpretation: no certification, protected text reproduction or award prediction.

LIVING EXPERIMENT · TOWER

The Tolerance Control Tower

Work packages move through delegated airspace. Forecast breaches trigger visible escalation; hidden variance cannot land as a surprise.

MODEL STATESME · SENSE · APPLYDeterministic teaching model · no award prediction
Organisation size
Depth

ORIGIN × EVOLUTION × CURRENT PRACTICE

Why this reference exists—and what changed.

Public-sector, technology, infrastructure, professional-services and controlled project environments using defined governance and escalation.

01 · 1975–1989

PROMPT and PRINCE origins

UK public-sector IT project methods evolved into PRINCE under the Central Computer and Telecommunications Agency.

02 · 1996

PRINCE2 becomes generic

The method expanded beyond IT and organised management around principles, themes/practices and processes.

03 · 2009–2017

Tailoring and practical use

Revisions simplified the method and strengthened tailoring, people and integration with varied delivery approaches.

04 · 2023–2025

Version 7 and 7.2 materials

PRINCE2 7 reframed themes as practices and strengthened people, sustainability, digital/data and compatibility; official materials received 7.2 updates.

Method terminology does not prove proportionate control. A bid must show how roles, products, tolerances and escalation fit the actual contract.

OFFICIAL SOURCE FRESHNESS MONITOR

SOURCE CHECK PENDING

Monthly official-source reachability and change review.

LAST SOURCE CHECKloading…
What this date means

The check records source reachability and a content fingerprint. It does not silently change the page or claim that an edition changed.

PUBLICLY DESCRIBABLE ANATOMY

Every domain gets a specific bid-management translation.

These are navigational interpretations, not substitute clauses. Use the official publication for normative wording.

Open official source ↗
  1. 01

    Seven principles

    Use the principles as non-negotiable tests of whether project governance remains recognisably PRINCE2.

    Evidence object
    Principle application and tailoring record
    Decision test
    Can the team show how each principle operates rather than merely naming it?
  2. 02

    People within the method

    Design roles, relationships, change adoption and communication around the people doing and receiving the project.

    Evidence object
    People and organisation design
    Decision test
    Is authority workable across buyer, supplier and user organisations?
  3. 03

    Seven management practices

    Apply the seven practices to business case, organisation, plans, quality, risk, issues and progress.

    Evidence object
    Practice-specific management products
    Decision test
    Does each practice produce a decision, not just a document?
  4. 04

    Seven processes

    Trace the seven processes from starting and directing through stages, delivery and closure.

    Evidence object
    Process and decision calendar
    Decision test
    Is every process adapted to the real commercial and delivery lifecycle?
  5. 05

    Business justification and product focus

    Keep business justification current and define products and acceptance before activities.

    Evidence object
    Business case and product descriptions
    Decision test
    Would the project stop if value no longer justified the investment?
  6. 06

    Management by stages and exception

    Divide delivery into manageable stages and escalate forecast tolerance breaches.

    Evidence object
    Stage plan, tolerances and exception route
    Decision test
    Are tolerances decision thresholds rather than reporting colours?
  7. 07

    Tailoring, sustainability and digital/data considerations

    Tailor for scale, delivery approach, sustainability and data without hollowing out governance.

    Evidence object
    Tailoring and digital/data strategy
    Decision test
    Can every omission be justified by context and risk?

BEFORE × INTERVENTION × AFTER

Worked case · staged infrastructure modernisation

A fictional programme replaces operational technology across 14 sites while keeping legacy service live.

A worked method translation, not PeopleCert endorsement or project-performance evidence.

BEFORE

What the team can observe

The bid has one master plan and monthly board but no product descriptions, tolerances, stage authority or stopping rule.

PRINCE2 INTERVENTION

What changes in the operating system

The team defines products and acceptance, divides work by decision risk, assigns board roles and creates exception and continued-justification tests.

The offer contains five controlled stages, 63 product descriptions and explicit tolerances that protect service continuity and commercial authority.

Products with acceptance criteria21 / 6363 / 63
Stage boundaries with decision1 / 55 / 5
Tolerances with escalation owner4 / 1515 / 15
Benefits without post-project owner60

PROPORTIONATE IMPLEMENTATION

Scale the control—not the integrity of the decision.

PRINCE2 is a governance method, not a complete delivery toolkit or guarantee of on-time delivery. It must be tailored without removing its control logic.

WORKED CASEPRINCE2–01Teaching scenario · no claimed outcome
Solo / micro

Combine roles but preserve justification, product, stage, exception and learning decisions.

Business case, product, stage decision

Bid team

Map bid promises into products, tolerances, stages and buyer/supplier governance.

Product map, stage model, exception route

Enterprise

Connect project boards, portfolio decisions and benefits ownership.

Directing decisions, assurance, closure

Mark only controls the worked team has actually completed.

01 · Requirement coverageNOT YET OBSERVABLECan every material requirement be located and owned?
02 · Evidence validityNOT YET OBSERVABLEIs proof current, relevant, approved and close to the claim?
03 · Decision integrityNOT YET OBSERVABLEAre authority, assumptions and trade-offs visible?
04 · Review effectivenessNOT YET OBSERVABLEDid independent challenge change the work before release?
05 · Rework exposureNOT YET OBSERVABLEHow much avoidable correction remains?
06 · Control driftNOT YET OBSERVABLECan commitments change without authorisation?
07 · Handover readinessNOT YET OBSERVABLECan delivery accept the promise without reinterpretation?
08 · Learning closureNOT YET OBSERVABLEDid feedback alter the next qualification, evidence or control?