Skip to content
0 / 66 sessions

Course contents

Module 6 of 13 · 66 sessions

PRINCE2® Foundation

Free
Course overview

Course progress

0%

0 of 66 sessions complete

Sign in to save your progress across devices.

Module 6Session 34 of 6613 minKnowledge check

Management stages

How to divide a project into management stages, and how they differ from the technical work inside them.

Sign in to track progress
Guided lesson
~0:22Scene 1 of 7

Scene 1

Management stages

How to divide a project into management stages, and how they differ from the technical work inside them.

Caption 1 of 3

Explain why projects are divided into management stages

0:00 / 0:22
Read all scene text
  1. Explain why projects are divided into management stages
  2. Decide on the number and length of stages
  3. Distinguish management stages from delivery steps

Scenes animate with GSAP. Use pause or replay at any time.

In this session

  • Explain why projects are divided into management stages
  • Decide on the number and length of stages
  • Distinguish management stages from delivery steps

It's time to decide where the York project's decision points should be.

Let's say Sam proposes two stages: initiation, then "everything else" for six months. Ruth is worried. "So the board approves £80,000 in one go and doesn't formally look again until it's open?"

Where should the board step in?

Select the arrow to learn more

1 of 4

Look for big decisions

After the building work, you'll know whether the damp has been fixed and what's left in the budget. That's a natural point to decide whether to fit out.

Why use stages

Management stages give the board:

  • Review and decision points, to check the business case is still valid
  • Control, by authorising one stage at a time
  • Planning horizons, so detailed plans cover only what can be planned well
  • A way to scale risk, using shorter stages where things are riskier

How many stages

Every PRINCE2 project has at least two management stages: the initiation stage and at least one more stage that delivers products.

Beyond that, it depends. Shorter stages give more control but mean more board decisions. Longer ones give the project manager more freedom. Think about the risk, the planning horizon, the board's availability and natural decision points.

Management stages vs delivery steps

Management stages are about decisions: they don't overlap, and each ends with a board review. Delivery steps are about technical work: design, build, test. These steps can overlap stages.

The shopfitting design starts in Stage 2 while the builders are still on site, so it's ready in time. That's fine. The management stage boundary is still the board's review after the building works.

Planning the stage boundary

Near the end of each stage, the project manager prepares for the boundary. Sam reports on the current stage, updates the business case and project plan, and drafts the next stage plan.

The board then reviews everything and decides whether to authorise the next stage. You'll see this in detail with the managing a stage boundary process.

Key points to remember

  • Management stages are sections of the project authorised one at a time.
  • Every project has at least two: initiation and at least one delivery stage.
  • Stage length balances control, risk and the planning horizon.
  • Management stages don't overlap; delivery work can cross stage boundaries.
Knowledge checkQuestion 1 of 4

Knowledge check

True or false

Practices

Management stages can overlap.

Management stages can overlap.
Choose one answer to continue.

Sign in to save your result. Knowledge checks can be retried any time.

PRINCE2® is a registered trademark of the PeopleCert group. MockAcademy is independent and not affiliated with, endorsed by or licensed by PeopleCert.