PRINCE2 Principles Aspects Processes

Stefan Coetzeecreated 2026-05-12updated 2026-06-083 min readframework-concept
Vault note, not reviewed against the source. Written in the knowledge vault on 2026-05-12 by models working with Stefan Coetzee and published as it stands, with private addresses, e-mail addresses and an employer name redacted. Check claims against the primary source before relying on them.

PRINCE2 Principles, Aspects, Processes

Seven principles

  1. Continued business justification — viable business case throughout.
  2. Learn from experience — lessons captured + applied.
  3. Defined roles, responsibilities and relationships — clear authority.
  4. Manage by stages — break into stages with go/no-go gates.
  5. Manage by exception — defined tolerances; escalation when exceeded.
  6. Focus on products — outputs over activities.
  7. Tailor to suit the project — adapt method to context.

Seven aspects (PRINCE2 7 — formerly "themes")

1. Business case

Why? Documented business justification. Reviewed at stage boundaries.

2. Organisation

Who? Project management team structure, roles, responsibilities. Includes:

  • Project Board (Executive, Senior User, Senior Supplier)
  • Project Manager
  • Team Manager(s)
  • Project Assurance
  • Project Support
  • Change Authority

3. Plans

How / when / cost? Hierarchy:

  • Project Plan (whole project)
  • Stage Plan (per stage)
  • Team Plan (work package level)
  • Exception Plan (when tolerances exceeded)

4. Risk

What if? Risk management approach + risk register. Threat / opportunity treatment.

5. Issues

What's the impact? Issue register. Issue resolution paths: request for change, off-specification, problem/concern.

6. Progress

Where are we? Control mechanisms:

  • Stages
  • Tolerances (time, cost, scope, quality, benefits, risk)
  • Reporting (highlight reports, end-stage reports)

7. Quality

What's required? Quality management approach + product description quality criteria + quality register.

Sustainability (added in PRINCE2 7)

Sustainability considerations woven through aspects — not standalone in all readings.

Seven processes

1. Starting up a Project (SU)

Pre-project activity. Output: Project Mandate / Brief; Project Approach; project management team.

2. Initiating a Project (IP)

Define project. Output: Project Initiation Documentation (PID); plans; registers; controls.

3. Directing a Project (DP)

Project Board level throughout project. Outputs: authorization decisions; ad-hoc direction; escalation handling.

4. Controlling a Stage (CS)

Project Manager day-to-day. Work package authorization; issue/risk handling; reporting.

5. Managing Product Delivery (MP)

Team Manager level. Execute work packages; quality checks.

6. Managing a Stage Boundary (SB)

End of stage. Stage Plan completion; next Stage Plan; review; go/no-go decision.

7. Closing a Project (CP)

End of project. Confirm completion; lessons; handover.

Tailoring

Tailoring guidance per:

  • Project context (small/large, simple/complex, internal/commercial, agile/waterfall).
  • Sector specifics.
  • Hybrid approaches (PRINCE2 Agile).

Tailoring should preserve principles; can adapt processes and templates.

Roles and responsibilities

  • Project Board: governance.
    • Executive: business interest.
    • Senior User: user interest.
    • Senior Supplier: supplier interest.
  • Project Manager: day-to-day leadership.
  • Team Manager: work-package delivery.
  • Project Assurance: independent verification (often delegated by Board members).
  • Project Support: administrative + tool support.
  • Change Authority: change-decision authority (typically Project Board or delegated).

Management products

PRINCE2 defines management products:

  • Project Initiation Documentation (PID)
  • Project Brief
  • Project Plan / Stage Plan / Team Plan / Exception Plan
  • Business Case
  • Risk Register / Issue Register / Quality Register / Lessons Log
  • Daily Log
  • Configuration Item Records
  • Highlight Reports / End Stage Reports / End Project Report / Lessons Report
  • Product Descriptions
  • Work Packages
  • Many specialist products (project-specific deliverables)

PRINCE2 vs Scrum / Agile

  • PRINCE2 = project method (governance + control + delivery framework).
  • Scrum = work-management framework (iterative delivery).
  • Compatible: PRINCE2 Agile combines both.

PRINCE2 vs PMBOK

  • PRINCE2 = methodology (prescriptive).
  • PMBOK = body of knowledge (descriptive).
  • Different traditions; complementary.
  • Many practitioners hold both certifications.

SRE and AI-agent fit notes

For governance of significant projects:

  • AI feature delivery projects can use PRINCE2 structure.
  • Stages aligned with AI feature lifecycle.
  • Tolerances managed via PRINCE2 reporting.

Stefan-context implementation sketch

  • For solo / small-team: PRINCE2 overhead disproportionate.
  • For UK / EU public-sector engagements: PRINCE2 vocabulary often expected.
  • For multi-month delivery projects: tailoring useful.

See also