End Project Report.docVIP

PRINCE2?- End Project Report Project Name: Date: Release: Draft/Final Author: Owner: Client: Document Number: Note: This document is only valid on the day it was printed Revision History Date of next revision: Revision Date Previous Revision Date Summary of Changes Changes Marked Approvals This document requires the following approvals. A signed copy should be placed in the project files. Name Signature Title Date of Issue Version Distribution This document has been distributed to: Name Title Date of Issue Version Overview Purpose An End Project Report is used during project closure to review how the project performed against the version of the Project Initiation Documentation used to authorize it. It also allows the: Passing on of any lessons that can be usefully applied to other projects Passing on of details of unfinished work, ongoing risks or potential product modifications to the group charged with future support of the project’s products in their operational life. Contents The End Project Report should cover the following topics. Project Manager’s report 3 Review of the Business Case 3 Review of Project Objectives 3 Review of Team Performance 4 Lessons Report 4 Review of Products 5 Advice The End Project Report is derived from the: Project Initiation Documentation; Business Case; Project Plan; Benefits Review Plan; Issue Register, Quality Register and Risk Register; Lessons Report and End Stage Reports (and Exceptions Reports, if applicable). An End Project Report can take a number of formats, including presentation to the Project Board (physical meeting or conference call), as a document or email issued to the Project Board or as an entry in a project management tool. The following quality criteria should be observed: Any abnormal situations are described, together with their impact At the end of the project, all issues should either be closed or become