<Project Name>
Post Project Checklist (M192)
Project Name:
PlanView Number:
Project Sponsor:
Project Size:
Project Director:
Project Start Date:
Project Manager:
Project End Date:
Fill in the project information table below. This table must be completed in all deliverable documents related to the
project. In addition, all documents must include the project name in the title bar (above) and in page headers
(beginning with Page 2 of each document). Delete this instructional paragraph from your final draft.
YES
NO
N/A
Risks, Issues, and Scope Management Process
1. Are all outstanding risks, mitigation, issues, scope, and resolution logs closed?
Comments:
2. Has final documentation been prepared on status against outstanding actions?
Comments:
3. Has the online repository and service documentation database been updated and
archived? Comments:
Team Status Meeting/Reporting
4. Have status reports been “bundled” in one place for final project documentation
turnover/archival?
Comments:
5. Has the project team prepared a final project status report?
Comments:
Project Status Reporting
6. Has a final Project Status report been prepared for your Stakeholders?
Comments:
7.
Please send a note to Rob Thomas (thomasrl@umich.edu) with the Project
Name/PlanView # so that he knows the project was completed and can include it in
his All Staff Update for the project calendar. (Big Sheet)
Stakeholder Status Review
8. Has a final Project Status Review meeting with the Stakeholders been held?
Comments:
9. Complete the Project Closure Executive Summary. Project Managers should draft
the summary and review it with the Project Director and Steering Committee where
appropriate. The summary is due within 45 calendar days of your project golive/completion. When complete, the report is stored in the project documentation
repository and also sent via email to Rob Thomas (thomasrl@umich.edu).
M192 Post Project Checklist v.1.0
Document1
Page 1 of 3
<Project Name>
YES
NO
N/A
10. Has the project conclusion been acknowledged? Was acknowledgement obtained on
the project as verification of the completion of all project execution activities?
Comments:
Lessons Learned
11. Have the Lessons Learned been archived?
Comments:
12. Has the Lessons Learned Summary been prepared and reviewed?
Comments:
Project Notebook
13. Has the project notebook / binder (repository) containing all required materials been
archived?
Comments:
14. Are confidential project materials, if any, archived?
Comments:
Final Reminders
15. Officially close out vendor or other contracts, if any.
Comments:
16. Complete facilities project shutdown tasks, such as returning borrowed materials,
returning security badges for contractors, etc.
Comments:
17. Be sure that tools used in project tracking and control, such as Project Plan, Project
Definition, Project Notebook, and Project Score Card, are finalized and are archived
appropriately. Move the "Inactive" project to the ITS Archived Project directory
and/or onto a CD. Be sure that Lessons learned have been recorded. These tools
document the history of the project, and it is important for them to be complete and
accessible for reference.
For projects stored in SharePoint, put in request to have site moved to ‘Product’ or
other section where appropriate as a permanent location so the project information is
maintained and accessible once the project closure is completed.
Comments:
18. Populate the Key Service Document repository with all required documentation for
each of the services being moved from Project state to the Run state.
https://sites.google.com/a/umich.edu/its-key-service-document-repository/
Comments:
19. Coordinate with ITS management to release Project Team Members and provide
input regarding performance on the project.
Comments:
20. Complete review of work efforts for Rewards and Recognition of project team
members.
21. Update the Service Definition/ Service Level Expectation (SLE) if needed
Link to SLE repository and template: https://sites.google.com/a/umich.edu/its-key-servicedocument-repository/?pli=1
M192 Post Project Checklist v.1.0
Document1
Page 2 of 3
<Project Name>
Document Change Control is a fixed section of all project management document templates. This section tracks the revision
history of the template and indicates the most current version in effect. Include this section, as is, in your final document as a
separate, last page. Delete this instructional paragraph from your final draft.
Internal Use Only
Document Change Control
Post Project Checklist (M192)
Version
Number
Date
Revision
Author
Description
1.0
05/22/08
PSM-KS
2.0
11/24/08
PSM-ISPS
2.1
8/27/10
PSM-KS
3.0
12/10/12
EB
Updated to include reference to Key Service Document Repository
4.0
8/23/2013
EB
Updated link to Key Service Document Repository to Google site address
5.0
10/15/2013
JM
Updated to add SLE Repository and Template. Updated Logo.
Converted to .docx format; added new MAIS logo to header.
Inserted new step 7 in Project Status Reporting section to notify Rob
Thomas of project closure to include in Big Sheet. Added Step 9 for
Executive Summary completion. Added SharePoint directions to Step 17.
Removed EAS reference from Step 1. Added Step 19 for Rewards and
Recognition.
Updated to include references to ITS
This document is owned and maintained by ITS Process and Service Management, Project Support. Any changes to template format
and content must adhere to departmental document management standards.
M192 Post Project Checklist v.1.0
Document1
Page 3 of 3