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.
Respond to each question. For each “no” response, include an issue in Open Issues section.
Do you agree that the product and/or service is ready to be deployed?
Do you agree the product and/or service has sufficiently met the stated business goals and objectives?
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?
Do you agree the project should be closed? If no, please explain:
Rate your level of satisfaction with regards to the project outcomes listed below
List resources specified in the Project Plan and used by the project.
(e.g., Contractor, 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.
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.
Post-Implementation Review of Business Outcomes (actual review)
Post-Implementation Review of Business Outcomes (approval)
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.