PRINCE2 and Structured Project Management Methods

EverythingEverything else in this series — Waterfall, Agile and its family, the scheduling techniques — describes how work gets sequenced and delivered. PRINCE2 answers a related but distinct question: how is a project governed? Who has authority to approve spending, who can kill the project, what evidence justifies it continuing to exist at all. It's the most widely used answer to that question in UK government and public-sector work specifically, and it connects directly to the previous page's territory — one of its core components is quality management, built explicitly around the same discipline as ISO 9001.

A UK Government Standard, Not a Generic Framework

PRINCE2'sPRINCE2's lineage runs through UK government IT procurement specifically. Its predecessor, PROMPT II, was adopted by the Central Computer and Telecommunications Agency (CCTA) in 1989 as the UK government's standard for managing IT projects, under the name PRINCE — originally short for "PROMPT II IN the CCTA Environment," later reworked into the more memorable backronym "PRojects IN Controlled Environments"¹. The original PRINCE gained a reputation for being heavyweight and rigid, applicable mainly to large government projects; a 1996 revision, developed with input from around 150 European organisations, produced PRINCE2 — a genuinely generic method no longer tied to IT projects specifically, which is the version still in use (and still being revised — a 7th edition restructured the "themes" as "practices") today¹.

Structure: Principles, Themes, Processes

PRINCE2PRINCE2 organises itself around three interlocking components, plus a mandatory instruction to tailor all of them to the actual project rather than apply them mechanically²:

Component	What it covers	Example
7 Principles	Non-negotiable guiding rules for any PRINCE2 project — if a principle isn't being followed, the project isn't really running PRINCE2, whatever it's calling itself.	"Continued business justification" — a project must be able to demonstrate, at every stage, that it's still worth doing; if the business case fails, PRINCE2 says stop, not push on to protect sunk cost.
7 Themes (practices, in the 7th edition)	Aspects that must be addressed continuously throughout the project, not just at the start.	Quality — the theme most directly relevant here (see below); others include Risk, Business Case, Organization, Plans, Change, and Progress.
7 Processes	The actual chronological journey a project moves through, from before it's formally authorised to formal closure.	Starting Up a Project → Initiating a Project → (repeated) Controlling a Stage → Closing a Project, among others.

The Quality Theme: PRINCE2's Direct Link to ISO 9001

PRINCE2'sPRINCE2's Quality theme is where this page connects directly to Quality Management Systems: its central mechanism is a quality register, a living document defining the acceptance criteria and quality standard for every deliverable the project produces, checked against as the project proceeds³. This is the same underlying discipline as an ISO 9001 QMS — documented standards, checked systematically, with records proving the check actually happened — applied at the scale of one project's deliverables rather than an entire organisation's processes. A project run under PRINCE2 inside an organisation that's separately ISO 9001 certified isn't running two unrelated systems; the project's quality register is typically how that project satisfies the organisation's own QMS obligations for that specific piece of work.

"and Similar": PMBOK and the Prescriptive/Descriptive Split

PRINCE2'sPRINCE2's most common point of comparison is the Project Management Institute's PMBOK Guide (A Guide to the Project Management Body of Knowledge)⁴, the dominant standard in North America and the basis of the PMP certification. The useful distinction, not always stated clearly, is that PRINCE2 is prescriptive — it specifies what should be done, by whom, and when, as an actual method — while PMBOK is descriptive: a structured body of knowledge and technique across defined knowledge areas, without mandating a single sequence of processes to run⁵. In practice the two aren't rivals so much as different altitudes: PMBOK gives a practitioner a toolbox of techniques (many genuinely overlapping with what this whole series covers — a WBS, a Gantt chart, risk registers), while PRINCE2 gives a specific governance process to run a project through. It's entirely normal, and common in practice, for an organisation to run PRINCE2 as its governance framework while its project managers draw individual techniques from PMBOK's wider toolbox.

Where PRINCE2 sits relative to the delivery methodologies covered elsewhere in this series is worth being precise about: it operates one level up. PRINCE2 governs whether and how a project is authorised, controlled, and closed — it has almost nothing to say about whether the actual delivery work inside a stage runs as Waterfall or Scrum. A PRINCE2-governed project can, and often does, run agile delivery inside its stage boundaries — see Hybrid Waterfall/Agile for exactly this pattern under a different name.

References