PRINCE2 (PRojects IN Controlled Environments) is a process-based project management methodology developed in 1989 by the UK government and maintained by Axelos (now PeopleCert). Unlike Agile frameworks that focus purely on delivery cadence, PRINCE2 embeds governance and business justification directly into every decision point—requiring projects to remain continuously justified or face termination. This principle-driven approach, refined through the 7th edition (2023), now explicitly recognizes the "People" element alongside its traditional emphasis on products, stages, and control. PRINCE2's structured framework of 7 principles, 7 practices, and 7 processes makes it particularly effective for government, healthcare, IT, and construction sectors where accountability, risk management, and regulatory compliance are paramount. The methodology's explicit tailoring principle ensures it scales from small team initiatives to large enterprise transformations.
What This Cheat Sheet Covers
This topic spans 14 focused tables and 96 indexed concepts. Below is a complete table-by-table outline of this topic, spanning foundational concepts through advanced details.
Table 1: PRINCE2 Seven Principles
| Concept | Example | Description |
|---|---|---|
Project canceled mid-stream when market conditions eliminate ROI | • Every project must remain viable throughout its lifecycle &bull • Business case reviewed at each stage boundary &bull • No business case = no project &bull • Executive accountable for justification | |
Lessons log captures "sprint retrospectives take too long" → next stage reduces to 30 minutes | • Lessons sought, recorded, acted upon throughout project lifecycle &bull • Lessons log maintained from startup &bull • Lessons report created at closure &bull • 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 &bull • Separates directing (Board), managing (PM), and delivering (Team Manager) levels &bull • Project Assurance provides independent oversight | |
18-month project divided into 3-month stages with formal approval gates | • Project divided into management stages for control &bull • Board authorizes one stage at a time &bull • Enables go/no-go decisions &bull • Limits commitment of resources and risk exposure |