4 PAGES
Project Closure Report
Project Closure Report
Project Name:
Department:
Focus Area:
Product/Process:
Prepared By
|
Document Owner(s) |
Project/Organization Role |
|
|
|
|
|
|
|
|
|
Project Closure Report Version Control
|
Version |
Author | ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note: For standard sections of the Project Closure Report template that have been excluded from the present document, the section headings have been moved to the Project Closure Report Sections Omitted list at the end.
TABLE OF CONTENTS
1 PROJECT CLOSURE REPORT PURPOSE 4
2 PROJECT CLOSURE REPORT GOALS 4
3 PROJECT CLOSURE REPORT SUMMARY 4
3.1 Project Background Overview 4
3.2 Project Highlights and Best Practices 5
3.3 Project Closure Synopsis 5
4 PROJECT METRICS PERFORMANCE 6
4.1 Goals and Objectives Performance 6
4.2 Success Criteria Performance 6
4.3 Milestone and Deliverables Performance 6
4.6 Metrics Performance Recommendations 6
5.5 Communication Management 6
5.6 Customer Expectation Management 6
5.10 Project Closure Recommendations 6
6 PROJECT CLOSURE REPORT APPROVALS 6
7.1 Project Closure Report Sections Omitted 6
PROJECT CLOSURE REPORT PURPOSE
|
Project Closure Report Purpose |
|
[Replace this text with your own statement of purpose, or use the following sample.]
The Project Closure Report is the final document produced for the project and is used by senior management to assess the success of the project, identify best practices for future projects, resolve all open issues, and formally close the project.
|
PROJECT CLOSURE REPORT GOALS
|
Project Closure Report Goals |
|
[Replace this text with your own statement of goals, or use the following sample.]
This Project Closure Report is created to accomplish the following goals: · Review and validate the milestones and success of the project. · Confirm outstanding issues, risks, and recommendations. · Outline tasks and activities required to close the project. · Identify project highlights and best practices for future projects.
|
PROJECT CLOSURE REPORT SUMMARY
Project Background Overview
|
Project Background Overview |
|
[Replace this text with a brief description of the project background. · What were the original goals, objectives, and success criteria? · Refer to project overview statement and/or project charter for this information.]
|
Project Highlights and Best Practices
|
Project Highlights and Best Practices |
|
Project Highlights: · ·
Best Practices: · ·
|
Project Closure Synopsis
|
Project Closure Synopsis |
|
[Replace this text with a brief description of 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, etc.)?]
|
PROJECT METRICS PERFORMANCE
Goals and Objectives Performance
|
Goals and Objectives Performance |
|
[Replace this text with a comparison of actual project performance to project objectives.]
|
Success Criteria Performance
|
Success Criteria Performance |
|
[Replace this text with details of project performance in terms of targeted success criteria. · Were all criteria achieved? To what level of success? · If some criteria were not achieved, what were the reasons? Is achievement anticipated at a later date? · Who is responsible for measuring continued progress?]
|
Milestone and Deliverables Performance
|
Milestones and Deliverables Performance |
|
[Replace this text with an outline of actual performance of project milestones and corresponding deliverables. · Were all deliverables achieved with high quality and customer acceptance? · If not, what were the reasons? · Is achievement anticipated at a later date?]
|
Schedule Performance
|
Schedule Performance |
|
Project Schedule Overview:
Project Schedule Control Process:
Project Schedule Corrective Actions:
Project Schedule Integration with Managing Project:
|
Budget Performance
|
Budget Performance |
|
Project Budget Overview:
Project Budget Corrective Actions:
|
Metrics Performance Recommendations
|
Metrics Performance Recommendations |
|
[Replace this text with an outline of metrics performance recommendations for the future.]
|
PROJECT CLOSURE TASKS
Resource Management
|
Resource Management |
|
[Replace this text with an explanation of how resources were managed. · What resource needs changed during the project? · Outline the steps to be taken in shifting project resources to other projects. · Explain how project knowledge (IP) from project team members will be captured and retained for future projects.]
|
Issue Management
|
Issue Management |
|
[Replace this text with a list of any issues still outstanding at the end of the project. · Will each issue be resolved? · Who will continue to report on each issue's progress?]
|
Risk Management
|
Risk Management |
|
Project Risks Mitigated:
Outstanding Project Risks:
|
Quality Management
|
Quality Management |
|
[Replace this text with a description of how quality management processes were used and integrated into the project, and how quality control measures provided quality assurance.]
|
Communication Management
|
Communication Management |
|
[Replace this text with an outline of the project communication process. · How effective was the process? · What changes were made during the project?]
|
Customer Expectation Management
|
Customer Expectation Management |
|
[Replace this text with a brief description of how customer expectations were managed. · Did these expectations vary during the course of the project? If so, how?]
|
Asset Management
|
Asset Management |
|
[Replace this text with a list of assets remaining at the end of the project. · How will those assets be dispositioned? · Who will manage the disposition process?]
|
Lessons Learned
|
Lessons Learned |
|
[Replace this text with a list of successes and shortcomings to remember for the future. · Which activities and processes worked well? · Which could have been improved, and how?]
|
Postproject Tasks
|
Postproject Tasks |
|
[Replace this text with a list of outstanding issues for this project. · What actions are not yet completed? Who is responsible for them? · Which success criteria are not yet met? Which deliverables are not yet achieved? · Which training requirements are still outstanding? · This information can be summarized from details in the preceding sections.]
|
Project Closure Recommendations
|
Project Closure Recommendations |
|
[Replace this text with a list of recommendations arising from review of closure tasks. · The main recommendation would usually be to gain project closure approval from the Project Sponsor, including agreement that the project has fulfilled all of the requirements as documented and that the Project Sponsor is satisfied that all outstanding items have been satisfactorily addressed.]
|
PROJECT CLOSURE REPORT APPROVALS
Prepared By __________________________________
([Job Title])
Approved By __________________________________
([Job Title])
__________________________________
([Job Title])
__________________________________
([Job Title])
Approval Date __________________________________
APPENDICES
Project Closure Report Sections Omitted
·
·
Template courtesy of Microsoft Office Templates. Retrieved from http://office.microsoft.com/en-us/templates/results.aspx?qu=Project+Closure+Report&ex=1&av=all#ai:TC001141410|
Confidential
Document1
Last printed on 6/1/20041:22:00PM
Confidential Page 2 12/2/2014