Make project closeout checklist and answer question

sampleprojectcloseoutchecklist.docx

Appendix C – Project Close-out Checklist

Section 1. General Information

Section 2. Final Deliverable Checklist

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

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		\|_\| Electronic \|_\| Manual
3.4b	Project Charter		\|_\| Electronic \|_\| Manual
3.4c	Project Plan		\|_\| Electronic \|_\| Manual
3.4d	Budget Documentation and Invoices		\|_\| Electronic \|_\| Manual
3.4e	Status Reports		\|_\| Electronic \|_\| Manual
3.4f	Risks and Issues Log		\|_\| Electronic \|_\| Manual
3.4g	Final deliverable		\|_\| 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.

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.

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)

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.