Programme Management Office
Project closure form
Project title:
Project ID
Project Sponsor
Project Manager
Document Author

Document Control

Date / Version / Changed by / Reasons for Change
v0.1 / Initial draft

Distribution List

Name / Role / eMail

AIM OF PROJECT CLOSURE

The Project Closure document is the final document produced for the project and is used by the ISPMO to assess the success of the project, identify lessons learned for future projects, resolve all open issues, and formally close the project.
In completing the closure document the following will be accomplished:
  • A comparison between what the project set out to achieve verses what was actually delivered
  • A review of project timelines including project milestone timeline to highlight any variance from the project plan and the reason for that variance.
  • A review of the project budget to determine if any variance occurred.
  • To confirm if there are outstanding tasks, issues or risk which need attention after the project is closed.
  • To identify lessons learned as a result of this project. Lessons learned will be documented into the programme lessons learned repository from which future projects managers can refer.

1.ORIGINAL PROJECT OVERVIEW

Please state the original Objectives,Business Needs &Benefits of the project (refer to the project proposal for this information)
ORIGINAL OBJECTIVES
ORIGINAL BUSINESS NEEDS & BENEFITS
SUCCESS FACTORS / In the white space below, please state the original success factors of the project as stated by the Project Sponsor (refer to the project Charter for this information).

2.REVIEW OF PROJECT PERFORMANCE

2.1 WHY IS THE PROJECT CLOSING / In the white space below please indicate why the project is being closed.
  • Is it being closed because all project objectives and deliverables have been met or is it being closed for other reasons (loss of funding, shift in strategy?

2.2 OBJECTIVE & BENEFITS PERFORMANCE / In the white space below please provide detail of what was delivered as part of the project.
Were the project objectives met?
2.3 SUCCESS FACTOR / In the white space below please provide details of project performance in terms of success criteria identified by the project sponsor in the charter?
Does the sponsor deem this project a success? Were all criteria achieved?
If some criteria were not achieved, what were the reasons? Is achievement anticipated at a later date?
2.4 ORIGINAL START AND END DATE OF THE PROJECT / Planned Start Date (as per original project plan) / Planned Completion Date (as per original project plan)
2.5 ACTUAL START AND END DATE OF THE PROJECT / Actual Start Date (as per final progress report) / Actual Completion Date (as per final progress report)

3.REVIEW OF PROJECT MILESTONES

Please provide details of the performance of the projects milestones. Please list all project milestone in the original project plan
3.1 Milestone Name / Status
<Completed,
Will be completed as BAU, Cancelled / Planned completion date / Actual completion date / Comments
Were milestones completed successfully? If not please provide reason
Please document any deviation between the planned and actual dates and provide reasons why.
<Milestone 1 >
<Milestone 2>
<Milestone 3>
<Milestone 4>

4.REVIEW OF PROJECT BUDGET

In the white spaces below please provide details of project expenditure, any savings produced as a result of the project and details of the annual operational costs as a result of the project.In all cases please include VAT.
4.1 PROJECT BUDGET (as per approved project budget template) / Planning Budget / Actual Budget / Please note any deviation between the planned and actual budget of the project. Please explain the reasons for that deviation.
<item 1> / € / €
<item 2> / € / €
<item 3> / € / €
<item 4> / € / €
4.2 SAVINGS AS A RESULT OF THE PROJECT / Savings produced / Which DIT budget will benefit from the savings? / Comments
Were the savings a planning part of the project? Are the savings a once off or will the savings be realised on an annual basis
<Desc of savings 1> / €
<Desc of savings 2> / €
4.3ANNUAL OPERATIONAL COSTS / Budget required per annum / Subacc it will be budgeted to / Comments
€ / €
€ / €
€ / €
€ / €

5.LESSON LEARNED

Please list the key lessons learned as a result of the project. Lessons learned will be entered into a lessons learned repository and future project managers will be able to benefit from the experience of this project
What went well, what went badly, what was lacking and assessment of any tools
Lessons learned / What was impacted? / Suggested change \ improvement

6.FUTURE WORK

In the white space below identify any future work worth considering and the options for doing it
Next upgrade\ change required as a result of the project / When will it need to occur / Impact \ effort estimation

1 of 4