Skip to content
0 / 66 sessions

Course contents

Module 9 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 9Session 48 of 6613 minKnowledge check

Baselines and change control

Why approved products are baselined, and how change control stops unauthorised changes creeping in.

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

Scene 1

Baselines and change control

Why approved products are baselined, and how change control stops unauthorised changes creeping in.

Caption 1 of 3

Explain what a baseline is

0:00 / 0:18
Read all scene text
  1. Explain what a baseline is
  2. Explain the purpose of change control
  3. Describe the role of the product register

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

In this session

  • Explain what a baseline is
  • Explain the purpose of change control
  • Describe the role of the product register

It's time to see why some things can't just be changed on a whim.

Let's say Kit and Priya are chatting on site. Priya mentions it'd be nice to have the cake display a bit wider. Kit says, "No problem, we'll do it." Two weeks later, the wider display means the till doesn't fit and the invoice is £800 higher.

What went wrong?

Select the arrow to learn more

1 of 4

The design was agreed

The counter design passed its quality review and was approved. Everyone was working from it.

What a baseline is

A baseline is an approved version of a product that's used as a reference point. Once something is baselined, it can only be changed through formal change control.

Baselines include the plans, the business case, product descriptions and the products themselves, like the approved counter design.

Why change control matters

Change control doesn't stop change. It makes sure changes are:

  • Captured, so nothing changes without a record
  • Assessed for their effect on cost, time, quality, scope, benefits, risk and sustainability
  • Decided by someone with the authority to approve them
  • Implemented in a controlled way, with every affected product updated

The product register

The product register keeps track of the project's products, their versions and their status. It records which version is the current baseline and who holds it.

Remember Ellie's shared folder of drawings? That's the product register in practice. When the counter design changes from version 2 to version 3, the register shows which one the team should use.

Configuration management

Keeping track of product versions is called configuration management. It's usually handled by project support, and the approach is described in the issue management approach.

For the app, Ana's team uses a code repository to track versions. For York, it's a shared folder and a spreadsheet. The principle is the same: one current version, and a history of how it got there.

Key points to remember

  • A baseline is an approved version of a product used as a reference point.
  • Baselines can only be changed through formal change control.
  • Change control makes sure changes are captured, assessed, decided and implemented properly.
  • The product register tracks products, their versions and their status.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Practices

What is a baseline?

What is a baseline?
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.