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

Recommend project closure

Once the Project Manager has confirmed that the project can be closed, a closure recommendation should be raised to the Project Board.

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:

• Use the Communication Management Strategy to identify any organization or interested party who needs to know that the project is closing. Consider also communication activities for public relations and marketing opportunities at this point
• Close the project’s Issue Register, Risk Register, Quality Register, Daily Log and Lessons Log
• All project information should be secured and archived (in accordance with the Configuration Management Strategy) in order to permit any future audit of the project management team’s decisions, actions and performance
• Prepare and send a draft project closure notification for review by the Project Board, stating that the project has closed

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.