PRINCE2 - Closing a Project Process Tutorial

18.1 Closing a Project Process

Hello and welcome to PRINCE2® Foundation Certification course offered by Simplilearn. This lesson is about ‘Closing a Project’ process. One of the defining features of a PRINCE2® project is that it is finite, which means it has a start and an end. PRINCE2® recommends that certain activities should be performed as a part of ‘Closing a Project’ process.

18.2 Objectives

After completing this lesson, you will be able to: ?State the purpose and objectives of the ‘Closing a Project’ process ?List the activities in the ‘Closing a Project’ process

18.3 Purpose of Closing a Project

The purpose of the ‘Closing a Project’ process is to provide a fixed point at which acceptance for the project product is confirmed, and to recognise that objectives set out in the original Project Initiation Documentation have been achieved (or approved changes to the objectives have been achieved), or that the project has nothing more to contribute.

18.4 Closing a Project

The project management team is adjourned and its responsibilities terminated after the project is closed. Project costs should no longer be incurred once it is closed. This process provides an opportunity to ensure that all unachieved goals and objectives are identified so that they can be addressed in the future. During this process it is ensured that the ownership of the products is transferred to the customer. Closure activities should be planned as part of the Stage Plan for the final management stage.

18.5 Objectives of Closing a Project

The objective of the ‘Closing a Project’ process is to verify user acceptance of the project’s products, review the performance of the project against its baselines, ensure that the host site is able to support the products when the project is disbanded, asses the benefits that have already been realised, update the forecast of the remaining benefits and plan for a review of those unrealised benefits. Some of the issues may be pending even when the closure of the project is approaching. In such case, this process ensures that provision has been made to address all open issues and risks with follow-up action recommendations. The Project Board may close the project prematurely under some circumstances. The Project Board may decide premature closure in case the Business Case is no longer valid. If the project is being brought to a premature close, this process will still need to be executed, but may need tailoring to suit the actual project situation.

18.6 Closing a Project—Overview

The image shown depicts the interaction between ‘Closing a Project’, ‘Controlling a Stage’ and ‘Directing a Project’ processes.

18.7 Closing a Project—Activities

Similar to the ‘Controlling a Stage’ process, closing project activities are Project Manager oriented. The activities of this process are: prepare planned closure, prepare premature closure, hand over products, evaluate the project, and recommend project closure. Closure activities are part of Stage Plan of final management stage and the Executive informs corporate or programme management about the project closure.

18.8 Closing a Project—Activities (contd.)

As a part of ‘Closing a Project’ process, several management products are updated. The Project Plan is updated by the Project Manager and reviewed by the Project Assurance. The Product Status Account is created by Project Support and reviewed by Project Manager along with Project Assurance. The acceptance records are produced by the Project Manager and reviewed by the Project Assurance. The acceptance records should be approved by the Executive, Senior Supplier and Senior User. The Project Assurance also reviews the End Project Report and Lessons Report created by Project Manager. The Project Assurance reviews it. The registers such as Issue register, Risk Register, Quality Register, Daily Log and Lessons Log are closed by Project Manager. The draft project closure notification is prepared by the Project Manager. The Project Assurance reviews it.

18.9 Closing a Project—Exercise

Three exercises are given in the screen to test the comprehension of ‘Closing a Project’ process. Please take some time to understand the questions and note the answers.

18.10 Quiz

The quiz section will help to check your understanding of the concepts covered.

18.11 Summary

Here is a quick recap of what we have learnt in this lesson: The purpose of the ‘Closing a Project’ process is to provide a fixed point at which acceptance for the project product is confirmed, and to recognise that objectives set out in the original Project Initiation Documentation have been achieved. Similar to the ‘Controlling a Stage’ process, ‘Closing a Project’ activities are Project Manager oriented. As a part of ‘Closing a Project’ process, several management products are updated.

18.12 Thank You

In the next lesson, we will discuss Tailoring PRINCE2® to Project Environment.

Find our PRINCE2® Foundation and Practitioner Online Classroom training classes in top cities:


Name Date Place
PRINCE2® Foundation and Practitioner 4 Aug -12 Aug 2018, Weekend batch Your City View Details
PRINCE2® Foundation and Practitioner 18 Aug -9 Sep 2018, Weekend batch Your City View Details
PRINCE2® Foundation and Practitioner 25 Aug -2 Sep 2018, Weekend batch Your City View Details
  • Disclaimer
  • PMP, PMI, PMBOK, CAPM, PgMP, PfMP, ACP, PBA, RMP, SP, and OPM3 are registered marks of the Project Management Institute, Inc.

We use cookies on this site for functional and analytical purposes. By using the site, you agree to be cookied and to our Terms of Use. Find out more

Request more information

For individuals
For business
Name*
Email*
Phone Number*
Your Message (Optional)

By proceeding, you agree to our Terms of Use and Privacy Policy

We are looking into your query.
Our consultants will get in touch with you soon.

A Simplilearn representative will get back to you in one business day.

First Name*
Last Name*
Email*
Phone Number*
Company*
Job Title*

By proceeding, you agree to our Terms of Use and Privacy Policy