---
name: prince2
description: Use when asked about PRINCE2 (Projects IN Controlled Environments) — its process-based, product-based-planning, business-justification-driven approach — as a structured, phase-gated methodology contrasted with agile/Scrum (see scrum, agile-principles) rather than a replacement for project-management's general concepts.
---

# PRINCE2

PRINCE2 (**Pr**ojects **IN** **C**ontrolled **E**nvironments) is a
widely-used, structured project management methodology — a set of
processes, principles, and best practices guiding project managers from
initiation through closure.

## Key aspects

- **Process-based approach** — organized into defined processes
  specifying step-by-step activities and responsibilities across the
  whole project lifecycle, rather than leaving process design to each
  project team.
- **Focus on business justification** — a strong, continuously-validated
  business case is required to justify the project's investment and
  confirm alignment with organizational objectives — PRINCE2 explicitly
  expects this to be checked throughout the project, not only approved
  once at the start.
- **Clear roles and responsibilities** — specific, named roles for
  project management team members, reducing ambiguity about who
  decides what.
- **Tailoring to the project environment** — designed to scale and adapt
  to different project sizes, industries, and contexts, rather than
  being a rigid one-size-fits-all process.
- **Product-based planning** — plans focus on defining and delivering
  concrete project products/deliverables (closely related to
  [[project-scope]]'s deliverables concept and
  [[work-breakdown-structure]]'s deliverable-oriented
  decomposition).
- **Controlled project governance** — clear decision-making structures
  and defined project controls, so authority and accountability are
  explicit rather than assumed.
- **Flexibility and manageability** — structured guidance for managing
  risk, handling change, and maintaining communication and stakeholder
  engagement throughout.

## How PRINCE2 relates to agile methods

PRINCE2 is a phase-gated, process-heavy methodology, contrasted with
[[scrum]]'s and [[agile-principles]]'s iterative,
lighter-weight approach — PRINCE2 favors predictability and strong
upfront governance; agile methods favor adaptability and welcoming late
change. Neither is universally superior: PRINCE2 suits contexts needing
strong governance and predictable, staged delivery (common in UK
government and large regulated organizations); agile suits contexts
where requirements are expected to evolve significantly. Some
organizations run a hybrid, using PRINCE2 for overall governance while
delivery teams work in agile sprints underneath it — see
[[project-management]]'s waterfall/agile/hybrid comparison for
this choice in general terms.

## Common pitfalls

- **Treating PRINCE2's process rigor as incompatible with any
  adaptability** — the framework explicitly includes tailoring guidance;
  applying every process element with maximum ceremony regardless of
  project size misapplies it.
- **A business case validated once and never revisited** — PRINCE2
  expects ongoing business justification, not a one-time approval gate.
- **Unclear role assignment despite PRINCE2's role structure existing
  specifically to prevent that** — the framework provides defined roles;
  not actually assigning and respecting them defeats their purpose.
- **Assuming PRINCE2 and agile are mutually exclusive** — many
  organizations successfully combine PRINCE2's governance layer with
  agile delivery underneath it.

## Learn more

- [[project-management]] for the general methodology-choice context (waterfall/agile/hybrid) PRINCE2 fits within.
- [[scrum]], [[agile-principles]] for the contrasting iterative approach.
- [[project-scope]], [[work-breakdown-structure]] for the deliverable-focused planning concepts PRINCE2's product-based planning shares.