Module 18: Performing Controlled Shut down and Tailoring of the PRINCE2 Closing A Project Process

Lesson 1:  18.1 Closing a Project Introduction

Here you will learn how to check project product user acceptance to ensure that the business can support the products, review the baseline performance of the project and ensure that the project is closed in an orderly way. You will grasp to addressing all open issues and risks, with follow-on action recommendations, assess any realized benefits, and update the benefits management approach to include any post-project benefit reviews. You will understand the closing a project purpose and check that PID objectives have been achieved, and transfer ownership from project management team to the agreed owners.

Members Only 18.2 Closing a Project Context

Here you will learn how the context of closing a project provides a clear end to a project is always more successful than a slow drift into use, as it is a recognition that the original objectives have been met (plus any approved changes) and that responsibility for ongoing operations and maintenance of the products has been confirmed by the agreed owners You will grasp why closure activities should be planned as part of the final stage plan, as work is required to prepared information to the project board to obtain its authorization for project closure.

Members Only 18.3 Closing a Project Objectives

Here you will learn how one of the defining features of a project is that it is finite; it has a start and an end, and if the project loses this distinction, it loses some of its advantages over purely operational management approaches. You will understand the closing a project activities of prepare planned closure, confirm project acceptance, evaluate the project and request project closure along with their key management products. The same activities are carried for a premature close but with prepare planned closure activity replaced prepare premature closure. Note that there may be some approved products not yet delivered. The project board may advise ownership of some, or all of those products be transferred to the users.

Members Only 18.4 Closing a Project Activities

Here you will learn how if the project board instructs the project manager to close the project prematurely, the project manager must ensure that work-in-progress is not abandoned but salvage anything of value created to date and check that any project cancellation gaps are raised to the business. The project products must be passed to an operational and maintenance environment prior to the project closure. You will understand how to confirm project acceptance and check that the benefits management approach includes post-project activities to confirm benefits that cannot be measured until after the project product has been in operational use for some time.

Members Only 18.5 Closing a Project Activities Evaluation and Roles

Here you will learn how the closing a project activities, evaluation and roles lesson and the project manager recommended actions for the evaluate the project, and request project closure, are used and applied. You will grasp how the closing a project process is tailored with regard to the roles and responsibilities via the RACI table are used.

Members Only 18.6 Applying Practices to Closing a Project

In this module there are 6 PRINCE2 video lessons covering the five activities needed for the controlled shut down of any PRINCE2 project -- 'Applying Practices to Closing a Project' In this lesson, you will learn how the seven PRINCE2 practices (business case, organizing, plans, quality, risks, issues and progress practices) are applied to the closing a project process. You will also grasp how the various documents, registers and management approaches are used.