Project Closeout_joe
- 1. All Singles Social Media Website Project Closeout and Assessment Report Version 2 ● 9-Mar-15
- 2. 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 Paul-Lattaer Rutledge Project Manager 4-April-15 Gerod Brown Legal 4-April-15 Group Wise INC. Project Sponsor 4-April-15
- 3. Section 1. General Information Project Name All Singles Social Media Website Project Start Date Project End Date 12-Jan-15 20-April-15 Project Sponsor(s) Title Department Division Group Wise INC. NA NA NA Project Manager Title Department Division Paul-Lattaer Rutledge PM NA NA 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 are 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 <Insert Project Name> Page 3 of 8 GNU Project Closeout and Assessment
- 4. 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 future reference? Yes No 3.4 Identify the storage location for the following project documents items: Item Document Location (e.g., Google Docs, Webspace) Format 3.4a Business Case (1)On Backups in ABC Smart LLC. Vault (2)Hard copy with Group Wise INC. Electronic Manual 3.4b Project Charter (1)On Backups in ABC Smart LLC. Vault (2)Hard copy with Group Wise INC. Electronic Manual 3.4c Project Plan (1)Hard copy with Group Wise INC. Electronic Manual 3.4d Budget Documentation and Invoices (1)Hard copy with Group Wise INC. Electronic Manual 3.4e Status Reports (1)On Backups in ABC Smart LLC. Vault Electronic Manual 3.4f Risks and Issues Log (1)On Backups in ABC Smart LLC. Vault Electronic Manual 3.4g Final deliverable (1)On Backups in ABC Smart LLC. Vault (2)Hard copy with Group Wise INC. Electronic Manual 3.4h If applicable, verify that final project deliverable for the project is attached or storage location is identified in 3.4. Section 4. Project Team List resources specified in the Project Plan and used by the project. <Insert Project Name> Page 4 of 8 GNU Project Closeout and Assessment
- 5. Name Role Type (e.g., Contractor, Employee) Paul-Lattaer Rutledge Project Manager Employee Shakim White Design Employee Tina Rome Team Leader Employee Joseph L Howard III Engineer Employee Gerod Brown Legal Employee Latarsh Williams Financial Employee Section 5. Project Lessons Learned Identify lessons learned specifically for the project. State the lessons learned in terms of a problem (issue). Describe the problem and include any project documentation references (e.g., Project Plan, Issues Log) that provide additional details. Identify recommended improvements to correct a similar problem in the future. Problem Statement Problem Description References Recommendation Delivery’s Servers not on site on time PM Order Eelier Stakeholder wanted top end server. Top end servers over budget Stakeholder/PM Increase Budget Section 6. Post-Implementation Support Plans Identify plans for post-implementation activities after project closeout. Refer to the Benefits Realization review gate for information about the Post-Implementation Review of Business Outcomes deliverable. Action Planned Date Assigned To Frequency Post-Implementation Review of Business Outcomes (actual review) Post-Implementation Review of Business Outcomes (approval) <Insert Project Name> Page 5 of 8 GNU Project Closeout and Assessment
- 6. Section 7. Open Issues Describe any open issues and plans for resolution within the context of project closeout. Include an open issue for any “no” responses in the Final Product and/or Service Acceptance Checklist and the Project Artifacts Checklist sections. Issue Planned Resolution NA NA NA NA NA NA NA NA <Insert Project Name> Page 6 of 8 GNU Project Closeout and Assessment
- 7. Section 7. Open Issues Describe any open issues and plans for resolution within the context of project closeout. Include an open issue for any “no” responses in the Final Product and/or Service Acceptance Checklist and the Project Artifacts Checklist sections. Issue Planned Resolution NA NA NA NA NA NA NA NA <Insert Project Name> Page 6 of 8 GNU Project Closeout and Assessment