ProjectCloseoutReport.doc

GNU Project Closeout and Assessment ReportVersion 1.0 ● 31-Jan-12 Approval of the Project Closeout and Assessment Report indicates an understanding and formal agreement that the project is ready to be closed. By signing this document, each individual agrees all administrative, financial, and logistical aspects of the project should be concluded, executed, and documented as described herein. Approver Name Title Signature Date Section 1. General Information Project Name Project Start Date Project End Date Project Sponsor(s) Title Department Division Project Manager Title Department Division Section 2. Final Deliverable/Deployment Checklist Respond to each question. For each “no” response, include an issue in Open Issues section. Item Question Response 2.1 Do you agree that the product and/or service is ready to be deployed? Yes No 2.2 Do you agree the product and/or service has sufficiently met the stated business goals and objectives? Yes No 2.3 Do you fully understand and agree to accept all operational requirements, operational risks, maintenance costs, and other limitations and/or constraints imposed as a result of ongoing operations of the product and/or service? Yes No 2.4 Do you agree the project should be closed? If no, please explain: Yes No Rate your level of satisfaction with regards to the project outcomes listed below 2.5 Project Quality Yes No 2.6 Product and/or Service Performance Yes No 2.7 Scope Yes No 2.8 Cost (Budget) Yes No 2.9 Schedule Yes No Section 3. Project Documentation Checklist Respond to each question. For each “no” response, include an issue in Open Issues section. Item Question Response 3.1 Have project documentation and other items (e.g., Business Case, Project Plan, Charter, Budget Documents, Status Reports) been prepared, collected, filed, and/or disposed? Yes No 3.3 Were audits (e.g., project closeout audit) completed and results documented for futur