Project Closeout Report

Tags

project management, document

You must be logged in to download this document

be first to review

01/28/2008 Page 1 Project Closeout Report Template v. 1.1 05/30/2006 Office of Enterprise Technology, Project Management Office State of Minnesota (Insert Agency Name Here) Project Closeout Report A. General Information Project Name: Date: (mm/dd/yyyy) Agency: Project Manager: In each of the following sections provide references to the location of the requested information and document successes, problems, and recommendations associated with that section. B. Final Acceptance Verify the Final Acceptance materials (provide reference): The results of the review of the product delivered compared to the baseline requirements and specifications. List of deviations; documented, approved, justified and future action plans Action items and issues closed or reassigned to the support organization References to other deliverables, key features and pertinent information about final product delivery Verification of final acceptance via signatures of the Executive Sponsor and key stakeholders Include statement that all product documentation has been transferred to the operations and maintenance organization and all required project documentation has been archived C. Staffing and Skills D. Project Organizational Structure E. Schedule Management Provide the baseline project schedules and final project schedules (provide reference). Project Schedule General Discussion 01/28/2008 Page 2 Project Closeout Report Template v. 1.1 05/30/2006 Office of Enterprise Technology, Project Management Office Schedule Control Schedule Corrective Actions Schedule Integration F. Cost Management Provide reference to the document (e.g., Monthly Status Report) that describes cost and budget results of the project in comparison to the baseline. Cost Budget Overview Corrective Actions G. Risk Management Provide reference to risk management artifacts that description of the major risks identified for the project and how they were handled. Risk Identification and Mitigation Risk Impact H. Quality Management Provide reference to quality control artifacts that describe how quality assurance was involved in this project. 01/28/2008 Page 3 Project Closeout Report Template v. 1.1 05/30/2006 Office of Enterprise Technology, Project Management Office I. Project Configuration Management Provide reference to the project artifacts that describe how the project configuration management process was utilized. J. Communications Management Provide reference to the artifacts that describe the project communication process, its effectiveness and any changes that had to be made to the communications plan during the project. K. Customer Expectations Management Describe how customer expectations were managed. Were expectations clear from the beginning? How were expectations different than expected? 01/28/2008 Page 4 Project Closeout Report Template v. 1.1 05/30/2006 Office of Enterprise Technology, Project Management Office L. Additional Lessons Learned Describe the successes, shortcomings, problems, issues, and recommendations for aspects not addressed above. Describe recommendations for process improvement and/or template modification. Describe new ideas that were successful in the project and make recommendations on how these processes might be adapted to other projects. M. Outcomes Assessment Report This report documents the extent the business objectives and anticipated benefits are achieved. In some cases this report cannot be completed until the product is in operation for three to six months, or until a particular business cycle has occurred. Document the responsibility and timeframe for producing the initial Outcomes Assessment Report. Responsibility: Scheduled Completion Date: N. Project Closure Sign-Off The Executive Sponsor and key stakeholders authorizes project closure by signing below. Name/Title Signature Date