Skip to content
0 / 66 sessions

Course contents

Module 12 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 12Session 63 of 6614 minKnowledge check

Closing a project

How to close a project in a controlled way: handing over, evaluating and passing on what remains.

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

Scene 1

Closing a project

How to close a project in a controlled way: handing over, evaluating and passing on what remains.

Caption 1 of 3

Describe the purpose of closing a project

0:00 / 0:20
Read all scene text
  1. Describe the purpose of closing a project
  2. Name the main activities in closing a project
  3. Explain how premature closure works

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

In this session

  • Describe the purpose of closing a project
  • Name the main activities in closing a project
  • Explain how premature closure works

It's time to close the York project.

Let's say the shop opened on 1 December. Customers are queuing, the chiller holds at 3°C and Priya is delighted. Sam's tempted to say "done" and move on to the app.

What still needs to happen?

Select the arrow to learn more

1 of 4

Hand over properly

Priya and Jo confirm the shop is accepted. Warranties, manuals and keys pass to the York team. Oakline's snagging list is agreed.

Purpose

The purpose of closing a project is to provide a fixed point at which acceptance of the project product is confirmed, and to recognise that the objectives have been achieved, or that the project has nothing more to contribute.

Main activities

Closing a project includes:

  • Prepare planned closure: confirm the products have been delivered and accepted
  • Prepare premature closure: if the board asks the project to close early
  • Hand over products to the users and operations
  • Evaluate the project: produce the end project report and lessons report
  • Recommend project closure to the board

Premature closure

Not every project closes as planned. If the business case stops being viable, the board can ask for premature closure.

Say the landlord had sold the building halfway through Stage 2. Sam would record what had been done, save anything useful, hand over what could be used and close the project in a controlled way, rather than just stopping.

After closure

Once the board authorises closure, the project management team is released. The project's records are archived according to the digital and data management approach.

Benefits realised after closure are tracked by the business layer, using the benefits management approach. York's payback is measured over two years, long after the project has closed.

Key points to remember

  • Closing a project provides a fixed point to confirm acceptance and close.
  • Its activities include handover, evaluation and recommending closure.
  • The board can request premature closure if the project is no longer justified.
  • Benefits realised after closure are tracked by the business layer.
Knowledge checkQuestion 1 of 4

Knowledge check

Choose one answer

Processes

Who authorises project closure?

Who authorises project closure?
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.