PRINCE2 Agile 2016
Previous Section   Next Section

A.8 End project report

A.8.1 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
  • 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.

A.8.2 Composition

  • Project manager’s report Summarizing the project’s performance
  • Review of the business case Summarizing the validity of the project’s business case:
    • Benefits achieved to date
    • Residual benefits expected (post-project)
    • Expected net benefits
    • Deviations from the approved business case
  • Review 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 project’s strategies and controls
  • Review of team performance In particular, providing recognition for good performance
  • Review of products:
    • Quality records listing the quality activities planned and completed
    • Approval records listing the products and their requisite approvals
    • Off-specifications listing any missing products or products that do not meet the original requirements, and confirmation of any concessions granted
    • Project product handover: confirmation (in the form of acceptance records) by the customer that operations and maintenance functions are ready to receive the project’s 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
  • Lessons report (see section A.15) 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).
Previous Section   Next Section