Closing a Project

• Purpose
• Objective
• Context
• Activities
  • Overview
  • Prepare planned closure
  • Prepare premature closure
  • Hand over products
  • Evaluate the project
  • Recommend project closure

Key sections

• Introduction
• Business case
• Organization
• Quality
• Plans
• Risk
• Change
• Progress
• Introduction to processes
• Starting up a projectDirecting a project
• Initiating a project
• Controlling a stage
• Managing Product Delivery
• Managing a Stage Boundary
• Closing a Project
• Tailoring PRINCE2 to the project environment
• Directing Projects with PRINCE2

Activities

Prepare planned closure

Before closure of the project can be recommended, the Project Manager must ensure that the expected results have all been achieved and delivered.

Diagram 1 shows the inputs to, and outputs from, this activity.

© Crown copyright 2005 Reproduced under licence from OGC

Diagram 1

PRINCE2® recommends the following actions:

• Update the Project Plan with actuals from the final stage
• Request a Product Status Account from Project Support. From the Product Status Account, ensure that the project’s products:
• Have been approved by the authorities identified in their Product Descriptions
• Meet all the quality criteria, or are covered by approved concessions
• Confirm that the project has delivered what is defined in the Project Product Description, and that the acceptance criteria have been met
• Seek approval to give notice to corporate or programme management that resources can be (or are about to be) released

Diagram 2 shows the responsibilities for this activity.

© Crown copyright 2005 Reproduced under licence from OGC

Diagram 2

PRINCE2® is a Registered Trade Mark of the Office of Government Commerce in the United Kingdom and other countries.