2. Closing a Project Objectives

The Project Manager carries out the work in Closing a Project, and the objectives are:

• Check that all required products have been delivered and accepted.

• Capture lessons learned in the Lesson Report, as this can be valuable for future projects.

• Ensure that the products can be supported after the project is disbanded.

• Hand over products to the customer, as described in the Configuration Management Strategy document.

• Evaluate the project by comparing project objectives with actuals, and write the End Project Report.

• Assess the benefits already realized and plan a review of benefits that will be realized after the project is complete.

4. Cp: Closing a Project Outputs

1. Closing a Project Outputs

The Closing a Project diagram shows that the Project Manager provides some documents to the Project Board and other documents to the Operations/Maintenance group who will support the products once the Project is complete.

Corp..

Corporate or Programme Management

www.Mgm tPlaza.com

Direction

Project Board

Directing a Project (DP)

Authorize a Stage or Exception Plan

Management

Project Manager

Authorize stage

End Stage Report Next Stage Plan or Exception Plan

Give ad hoc direction

Closure Notification

close soon

Auth. project closure

Highlight Reports

Advice

Premature Close

Closure Recommend. End Project Report FAR, Lessons Rpt Draft Closure Notificat.

CP

To: P ro je c t Bo a rd

ERP , LR, PP, BRP, draft PCN

To: Op s /Ma int.

FAR, Products, CIR

Exception Report

(Issue / Change & Risk)

(SB) Managing a Stage Boundary

Controlling a Stage (CS)

Closing a project (CP)

Clo s e d

LL, DL, RR, IR, QR

Clos in g a P ro ject outputs

• End Project Report

• Follow on actions recommendations

• Lessons Report

• Project Plan & Benefits Review Plan

• Project Closure Notification & CIR

Delivery

Team Manager

Based on OGC PRINCE2® material. Reproduced under license from OGC

Stages - Execution

Close

Fig 3.21 Closing a Project outputs

The documents given to the Project Board are:

• The End Project Report (ERP): This is written by the Project Manager and compares the project with the Project Initiation Documentation.

• The Lessons Report (LR): This records useful lessons that were learned during the project and can be applied to future projects.

• Other documents given to the project board are: Project Plan (PP), which has been kept up to date during the project, Benefits Review Plan (BRP), and draft Project Closure Notification.

The Project Manager provides the Operations / Maintenance group with:

• The follow on actions recommendations (FAR): This is a document that includes information on outstanding issues that are taken from the Issue and Risk Logs and requires follow-up action after the project has ended.

• The Project Manager also hands over product information, including the Configuration Item Records (CIR) for each product, to the operations and Maintenance Group.