Description of Change(s) MPMO Version January 2016 Closure Report <Programme/Project Title> <Programme/Project Number> Revision History Author Role Version Date Description of Change(s) Joe Bloggs V0.1 dd/mm/yy First draft.   Document Approval Name Signature Comments Purpose of this Document Reviews how the programme/project performed against what it set out to achieve (as detailed in the baseline Project Initiation Document (PID)). Confirmation that the Sponsor’s vision, scope, and overall deliverables of the programme/project, outlined in the Mandate and PID, have been fully met. Documents the passing on of the details of unfinished work, on-going risks, potential product modifications, to the group charged with future support of the solution ( i.e..BAU). Instructions When filling in this template, please delete the guidance text in green. In completing this document you should ensure: Any abnormal situations are described, together with their impact All issues have either been closed or become the subject of a follow-on action Any available and useful documentation or evidence should accompany the follow-on actions. Please contact your Local PMO, if you have any queries or suggestions about how this template can be improved.

Executive Summary Provide an overall summary of the programme’s/project’s performance. <Insert text here>

Explanation of Deviation (if applicable) Scope Review Review of how the programme/project performed against its scope baseline. <Insert text here> Scope Category Baseline Actual Explanation of Deviation (if applicable) Comments

Timeline & Delivery Plan Review Review of how the programme/project performed against its baseline timeline and Delivery Plan. <Insert text here> Insert plan on a page/timeline of baseline Delivery Plan Describe any deviation to key milestones dates Milestone Category Baseline Actual Explanation of Deviation (if applicable) Comments As in the baseline PID. What was achieved?

Explanation of Deviation (if applicable) Budget Review Review of how the programme/project performed against its baseline budget. <Insert text here> Budget Category Baseline Actual Explanation of Deviation (if applicable) Comments As at Stage Gate 2 Actual budget

Explanation of Deviation (if applicable) Benefits Review Expected Non-financial Benefits Outline the benefits that the programme/project set out to deliver and compare them to the actuals. If actuals are not just known, please state when these will be achieved. Expected Financial Benefits Quantitative Measure Forecast Actual Explanation of Deviation (if applicable) Comments Number of unwanted calls Yr1 Forecast Actual Yr2 Yr3 Yr4 Yr5 Comments Water CAPEX OPEX Waste Retail

RAIDO Review Risks Issues Assumptions Dependencies The RAIDO section below is used to record any major RAIDO’s that have not been resolved. Appropriate mitigation actions and owners must be identified, informed and also listed in the ‘Follow-on Actions’ section. Risks Issues Assumptions Dependencies ID Description Mitigation Action Owner Status Due Date ID Description Mitigation Action Owner Status Due Date ID Description Mitigation Action Owner Status Due Date ID Description Mitigation Action Owner Status Due Date

Project Handover Review List each of the programme/project support deliverables and who has/will take ownership. Any outstanding work associated with the handover or acceptance of the deliverables should be detailed in the ‘Follow-on Actions’ section. No Deliverable Business Owner Status Comments

Lessons Learned Successes Challenges Best Practices Lessons Learned Screenshot from the Lessons Learned Log - Used to record and pass on any lessons learned, best practices that will be useful to future programmes/projects and eventually be embedded into the standard ways of working. Successes   Challenges 1) 2) 3) Best Practices Lessons Learned What went well and the programme/project team is proud of? Unexpected events, that the programme/project team had to overcome? Things the programme/project team recommend, that future programmes/projects should always do? Things that the programme/project team, would do differently next time and want to highlight to others, in order to save them time and effort?

Follow-on Actions List each of the programme/project support deliverables and who has/will take ownership of these deliverables. Any outstanding work associated with the handover or acceptance of the deliverables should be detailed below: Action No Description Completion Date Owner