Hide Assignment Information
Instructions
Project Closure Report When a project has ended, whether in successful completion or in an unsuccessful termination, it is important to create a project closure report. This is often done through a sunset review process. This sunset review is sometimes referred to as the "last rites", "post mortem", "project debriefing", or other similar nicknames. A sunset review is designed to collect the challenges, solutions, and lessons of a recently completed project. It provides a forum where project participants can discuss what happened during the life of the project and identify what worked, what didn't, and how things can be done better in the future. Through the session, best practices and lessons learned can be captured for other project teams as well as future projects. The main objective of a project closure report is to provide a complete picture of the project, including both successes and failures. The report should include all important project information that would help stakeholders, auditors, and future PMs to clearly understand the project and how the work was completed. A project closure report discusses the success of the project and the lessons learned, documents project deliverables, and officially ends the project. It will also include relevant documents such as project charter, project closure checklist, etc. Assignment: Project Closure Report Using the guide below as a template, create a project report on the Denver Waterworks Case. You may not know the names of those involved, so titles will be sufficient for the distribution list. You will also not be able to gather much information about dates. Fill in as much detail as you can in these areas. Project Closure Report for: Date of Project Closure report: Distribution List: Project Background Overview/Project definition Project Overview Give a very brief summary of the project. Be sure to outline the project objectives. What were the goals? Project Dates Dates from project initiation to completion; enter major milestone dates such as design completion, product release, etc. Project Organization List all project participants including project team members, sponsors, end users, etc (and their roles within the project). Project Performance and Outcome Was the project successful? Compare the final project outcome with the planned project goal and objectives. Describe the success of the project in terms of achieving its intended objective and outputs.Were deliverables delivered on time and with customer acceptance? List any project deviations (in terms of scope, time resources, cost, delays) and reasons for those deviations. Were the quality objectives met (were there any)? List project models, methods, tools and processes used. Project Experiences/Observations Were there any unexpected impacts (positive or negative)? Describe unexpected impacts, positive or negative. Describe experience with the project management methods and tools. Unrealized/Outstanding Outputs List Outstanding items - Identify any remaining/outstanding items impacting project completion/closure (e.g. training for end users). Actions points required (on the outstanding items) - Identify actions items, due dates and responsibilities for above. If outstanding, what are next steps? Were any outputs unrealized? If so, how has this affected the overall impact on the project? List items that will not be implemented within the project. Explain if they were cancelled or deferred to another project. Improvement Recommendations and Comments Suggestions and Improvements - List suggestions for improvements for processes, methods, tools, cooperation, reporting, etc. Other Comments Closing remarks - List closing remarks or summary.