PRINCE2 (PRojects IN Controlled Environments) is a process-based project management methodology developed in 1989 by the UK government and now maintained by PeopleCert. Unlike Agile frameworks focused purely on delivery cadence, PRINCE2 embeds governance and business justification directly into every decision point—requiring projects to remain continuously justified or face termination. The 7th edition (2023) restructured the framework into five integrated elements (People, Project Context, Principles, Practices, Processes), added sustainability as a seventh performance target alongside time/cost/quality/scope/risk/benefits, and introduced four new management approach documents. In January 2026, PeopleCert rebranded the certification as PRINCE2 Project Management (Version 7). PRINCE2's 7-7-7 core structure—7 principles, 7 practices, and 7 processes—makes it especially effective in government, healthcare, IT, and construction sectors where accountability, defined governance, and regulatory compliance are paramount.
What This Cheat Sheet Covers
This topic spans 16 focused tables and 134 indexed concepts, 100 flashcards. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
A jump-to index of every table row in this cheat sheet.
An interactive map of every table and concept in this topic.
Table 1: PRINCE2 Seven Principles
All seven principles must be applied for a project to be considered a PRINCE2 project. They are universal — applicable regardless of project type, size, or industry — and provide the foundation for every other element of the methodology. They cannot be selected individually; applying fewer than all seven means the project is not following PRINCE2.
| Principle | Example | Description | |
|---|---|---|---|
Project cancelled mid-stream when market conditions eliminate ROI | • Every project must remain viable throughout its lifecycle • Business case reviewed at each stage boundary • No business case = no project • Executive accountable for justification | ||
Lessons log captures "sprint retrospectives take too long" → next stage reduces to 30 minutes | • Lessons sought, recorded, acted upon throughout lifecycle • Lessons log maintained from startup • Lessons report created at closure • Informs risk identification and planning | ||
Project Board (Executive, Senior User, Senior Supplier) provides governance; Project Manager handles day-to-day | • Clear accountability prevents gaps and overlaps • Separates directing (Board), managing (PM), and delivering (Team Manager) levels • Relationships explicitly emphasised in 7th edition • Project Assurance provides independent oversight | ||
18-month project divided into 3-month stages with formal approval gates | • Project divided into management stages for control • Board authorizes one stage at a time • Enables go/no-go decisions • Limits commitment of resources and risk exposure | ||
PM has ±10% time tolerance; exceeding triggers escalation to Project Board via exception report | • Tolerances define acceptable deviation across 7 aspects (time, cost, quality, scope, risk, benefit, sustainability) • Only exceptions escalate upward • Prevents micromanagement • Exception plan replaces current plan when tolerance breached | ||
Product breakdown structure (PBS) lists deliverables before creating activity schedule | • Projects deliver products (outputs), not activities • Product-based planning: PBS → Product Flow Diagram → Product Descriptions → schedule • Product descriptions specify quality criteria • Drives work package assignments | ||
Small project: single-page PID; large project: 50-page PID with detailed approach documents | • PRINCE2 must be tailored — not optional • Applies to all elements (processes, practices, products, roles) • Documented in PID and approved by Board • Balance control with administrative burden |