Skip to content
Tutorials Center
My learning

Topics

Lesson 11 of 41 ยท Initiation and Planning

PRINCE2 Overview

A clear introduction to PRINCE2: its seven principles, themes, processes and stages, the roles on a PRINCE2 project, how it compares with agile and how to tailor it.

PRINCE2 (PRojects IN Controlled Environments) is a process-based method for managing projects, widely used in the UK, Europe, Australia and international organizations and public bodies. It is a framework, not software: it tells you what to decide, who decides it and when, rather than how to do the technical work. Its main idea is control: a project is divided into stages, and the board decides at the end of each stage whether to continue.

The seven principles

Principles are the guiding rules. A project is only run "in the PRINCE2 way" if all seven apply.

  1. Continued business justification: there must be a reason to run the project, kept valid throughout.
  2. Learn from experience: look at past lessons at the start and record new ones.
  3. Defined roles and responsibilities: everyone knows who does what.
  4. Manage by stages: plan, delegate, monitor and control stage by stage.
  5. Manage by exception: define tolerances; escalate only when they will be breached.
  6. Focus on products: concentrate on the outputs and their quality criteria.
  7. Tailor to suit the project: adapt the method to size, complexity and risk.

The seven themes

Themes are aspects of project management that must be addressed continuously.

Theme Concern
Business case Why are we doing this and is it still worth it?
Organization Who does what, who decides?
Quality What do the products need to be fit for purpose?
Plans How, when and how much?
Risk Which uncertainties matter and what do we do?
Change How are issues and change requests handled?
Progress Where are we, and should we continue?

The seven processes

The processes describe the project life cycle.

flowchart LR
    SU[Starting up a project] --> IP[Initiating a project]
    IP --> DP[Directing a project]
    DP --> CS[Controlling a stage]
    CS --> MP[Managing product delivery]
    CS --> SB[Managing a stage boundary]
    SB --> CS
    SB --> CP[Closing a project]

Directing a project runs throughout; it is the board's decision-making layer.

  • Starting up a project: appoint the executive and project manager, capture the idea in a project brief.
  • Initiating a project: build the business case, plans, risk and quality approaches in the project initiation documentation.
  • Directing a project: the project board authorizes initiation, each stage, ad hoc changes and closure.
  • Controlling a stage: the project manager assigns work, monitors, reviews and reports.
  • Managing product delivery: the team builds the products.
  • Managing a stage boundary: plan the next stage and report on the one that ended.
  • Closing a project: confirm acceptance, hand over, evaluate and recommend closure.

Roles

The project board has three roles: the executive (owns the business case, ultimately accountable), the senior user (represents those who use the result) and the senior supplier (represents those providing the resources and expertise). The project manager runs the day-to-day work within tolerances; team managers lead delivery teams; project assurance checks the project independently; project support handles administration.

Management by exception and tolerances

The board does not review every task. It sets tolerances for time, cost, quality, scope, benefits and risk, such as "stage end date within 2 weeks of plan, cost within 10%". The project manager works freely inside the tolerances and raises an exception report only if the forecast shows they will be exceeded. That keeps senior time free and decisions timely.

Python Tolerance check and exception

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Stages

A PRINCE2 project has at least two stages: the initiation stage and one or more delivery stages. At each stage boundary the board decides whether the business case still holds. A long project can be split into stages so that progress is judged in shorter, manageable chunks.

Python Stage gate decisions

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

PRINCE2 and agile

PRINCE2 is about governance and control; agile methods are about how to deliver. They fit together: a PRINCE2 project can use Scrum inside a delivery stage, with the board seeing business-case health at stage boundaries. PRINCE2 Agile guidance exists exactly for this. The fixed-vs-flexible aspect differs: PRINCE2 tends to fix time and cost with flexible scope inside tolerances; in a pure agile team time and cost are fixed per iteration while scope varies.

PRINCE2 Agile (e.g. Scrum)
Focus Governance, control, business case Delivering value in short cycles
Planning Stage plans with tolerances Iteration plans, evolving backlog
Documentation Defined management products Just enough
Change Formal change control Welcome between iterations
Decisions Board at stage boundaries Product owner continuously

Tailoring and common mistakes

PRINCE2 is deliberately scalable. A small project can combine documents and use one-page reports; skipping the structure is the mistake, not slimming it down. Typical failures are treating it as paperwork, an absent executive, tolerances nobody uses and ignoring lessons.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What does 'manage by exception' mean in PRINCE2?

    Tolerances define the freedom of the project manager; exceeding them triggers escalation.
  2. 2. Who is the executive on the project board?

    The executive owns the business case and is accountable for the project's success.
  3. 3. At a stage boundary the board decides...

    Stage boundaries are formal decision points based on the business case.
  4. 4. How many principles does PRINCE2 have?

    PRINCE2 has seven principles, seven themes and seven processes.

Summary

  • PRINCE2 is a controlled, stage-based framework with seven principles, themes and processes.
  • The project board (executive, senior user, senior supplier) directs; the project manager manages within tolerances.
  • Management by exception frees senior people and speeds decisions.
  • It can be tailored and combined with agile delivery.

Next: Scope Management