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 36 of 6614 minKnowledge check

Estimating and prioritising

Techniques for estimating effort and cost, and for prioritising what to deliver when time or money is tight.

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

Scene 1

Estimating and prioritising

Techniques for estimating effort and cost, and for prioritising what to deliver when time or money is tight.

Caption 1 of 3

Describe common estimating techniques

0:00 / 0:16
Read all scene text
  1. Describe common estimating techniques
  2. Explain how prioritisation supports planning
  3. Apply MoSCoW prioritisation

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

In this session

  • Describe common estimating techniques
  • Explain how prioritisation supports planning
  • Apply MoSCoW prioritisation

It's time to put numbers on the plan and decide what matters most.

Let's say Sam needs a cost for the fit-out before Oakline has quoted. Kit is busy and can't price it for three weeks, but the board wants a stage 3 estimate now.

How can Sam estimate without the final quote?

Select the arrow to learn more

1 of 4

Compare

The Leeds shop fit-out cost £26,000 five years ago. York is a bit bigger and prices have risen. That gives a starting point of about £30,000.

Estimating techniques

Common estimating techniques include:

  • Top-down: estimate the whole, then split it across the parts
  • Bottom-up: estimate each part, then add them up
  • Comparative: use similar past projects, like the Leeds fit-out
  • Parametric: use a known rate, like cost per square metre
  • Data analytics: use data from past projects to predict effort and cost
  • Expert judgement: ask experienced people, sometimes using structured methods like Delphi or planning poker

Why prioritise

Plans rarely have room for everything everyone wants. Prioritising tells the team what to deliver first, and what to drop if time or money runs short.

This is especially important with iterative delivery. Ana's team delivers the most important app features first, so even if the project stopped early, the app would still be useful.

MoSCoW

MoSCoW is a popular prioritisation technique. Here's how Priya ranks features for the pre-order app:

  • Must have: order and pay for collection at York
  • Should have: save favourite orders
  • Could have: loyalty stamps
  • Won't have this time: home delivery

Estimates and tolerances

Estimates are never exact. That's one reason plans include tolerances. The board sets Stage 2 at £40,000 ±£3,000, which allows for estimates that are a little high or low without the board stepping in.

When an estimate turns out to be badly wrong, like the damp adding £5,000, the forecast goes outside tolerance and an exception plan may be needed.

Key points to remember

  • Use more than one estimating technique and compare the results.
  • Techniques include top-down, bottom-up, comparative, parametric, data analytics and expert judgement.
  • Prioritisation tells the team what to deliver first and what to drop.
  • MoSCoW ranks features as must, should, could and won't have this time.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Practices

What does the M in MoSCoW stand for?

What does the M in MoSCoW stand for?
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.