Closing a Project (CP) is a process within the PRINCE2 project management methodology. The Project Manager uses it to wrap up the project either at its premature end or planned closure.

What is it? Closing a project is the counterpart of the Starting Up a Project (SU) and Initiating a Project (IP). It allows the organisation take stock of project management performance and ensure that all unachieved goals and objectives are identified, ready to be addressed later.

Aims of the process are:-

 *Check everything has been delivered
 *Check that the end product is accepted
 *Make sure there are no loose ends
 *Store the project records for audit
 *Release resources

This process prepares the input for Confirming Project Closure (DP5), in which the Project Board brings the project to an end.

Why? Projects need to have a controlled close. This applies even if the objectives are not going to be met and is ended prematurely.

A failure to control the end of a project can mean a drift into operational management.

Who The central figure in Closing a Project is the Project Manager.

How There are a number of sub-processes involved in Closing a Project:-

 *Decommissioning a Project (CP1)
 *Identifying Follow-on Actions (CP2)
 *Evaluating a Project (CP3)

Management products include:-

 *End Stage Report
 *Archived Files
 *Follow-on Actions Recommendations
 *Post Project Review Plan
 *Project Closure Notification
 *Customer Acceptance
 *Operational/maintenance acceptance
 *Lessons Learned Report

As with all the other processes in PRINCE2, Closing a Project has to be tailored to take account of the project undertaken.

Related Articles
Xansa and Tesco Outsourcing
ITIL - programme
ITIL - PRINCE2
ITIL - lifecycle
ITIL - closure
ITIL - Change Authority