End Project Report

Created/updated 01/09/22PRINCE2- End Project ReportProject Name:Date:Release:Draft/FinalAuthor:Owner:Client:Document Number:Note: This document is only valid on the day it was printedRevision HistoryDate of next revision:Revision DatePrevious Revision DateSummary of ChangesChanges MarkedApprovalsThis document requires the following approvals. A signed copy should be placed in the project files.NameSignatureTitleDate of IssueVersionDistributionThis document has been distributed to:NameTitleDate of IssueVersion Crown copyright 2009. PRINCE2 is a Trade Mark of the Office of Government Commercepage 6 of 6End Project ReportCreated/updated 01/09/22OverviewPurposeAn 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 projects products in their operational life.ContentsThe End Project Report should cover the following topics. Project Managers report3Review of the Business Case3Review of Project Objectives3Review of Team Performance4Lessons Report4Review of Products5AdviceThe 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 the subject of a follow-on action recommendation Any available useful documentation or evidence should accompany the follow-on action recommendation(s) Any appointed Project Assurance roles should agree with the report.Project Managers report(Summarizing the projects performance)Review of the Business Case(Summarizing the validity of the projects Business Case)Benefits achieved to dateResidual benefits expected(post-project)Expected net benefitsDeviations from the approved Business CaseReview of Project Objectives(Review of how the project performed against its planned targets and tolerances for time, cost, quality, scope, benefits and risk. Review the effectiveness of the projects strategies and controls)Review of Team Performance(In particular, providing recognition for good performance)Lessons Report(A review of what went well, what went badly, and any recommendations for corporate or programme management consideration (and if the project was prematurely closed, then the reasons should be explained). This may be a separate document and referenced from this location)End Project ReportCreated/updated 01/09/22Review of ProductsProduct NameQuality Records Quality activities planned and completedApproval Records The Requisite approvals for each ProductOff-specifications Any missing products or products which do not meet the original requirements, and confirmation of any concessions grantedPlannedCompletedProject Product Handover(Confirmation (in the form of acceptance records) by the customer that operations and maintenance functions are ready to receive the projects product)Summary of Follow-on Action Recommendations(Request for Project Board advice about who should receive each recommended action. The recommended actions are related to unfinished work, ongoing issues and risks, and any other activities needed to take the products to the next phase of their life)