PROJECT CLOSEOUT

Project Closeout Checklist <Remove this section for final document>

Schedule Project Closeout Meeting to assess project results and verification of
deliverables
Ensure that ITS resources have entered time in ITS Time-Tracking System
Close project in appropriate systems
o ITS Time-Tracking
o MIS Project Tracking if applicable
Remove any network access, drive mappings no longer required
Knowledge Transfer with Clients
Cancel conference rooms reservations or dial-in numbers for standing meetings
Return equipment no longer required
Copy Novell drive from Active to Complete
Notify Project Team that project has been closed via email and PRC meeting
Ensure all documentation is up to date and stored in appropriate project folder for
archiving

May 12 2010

PAGE 1 OF 4
Template Version 2.0

Project Closeout

PROJECT CLOSEOUT
<The section below should be copied directly from the Project Scope Statement>

Project Work ID <Remedy ID>

Project Title: <Meaningful Title for Project>
Prepared by: <Name of Project Manager>
Date of Document: <MM/DD/YYYY>

1. PROJECT DESCRIPTION
<The section below should be copied directly from the Project Scope Statement>

1.1. Project Scope

1.1.1. High Level Requirements/Deliverables
1.1.1.1.
1.1.1.2.
1.2. Project Completion Criteria
1.2.1. Completion of all deliverables
1.2.2. User Acceptance Testing and Signoff of all deliverables

2. LESSONS LEARNED
2.1. List of positive impacts to the project<Based on discussions with Client in Project Closure Meeting, list of items
and/or task that went well on the project and had a positive impact to the outcome of Deliverables>

2.1.1.
2.1.2.
2.2. List of improvements that could be made for future related projects<Based on discussions with
Client in Project Closure Meeting, list of items and/or task that could have been done better and can be improved upon for the future as it
relates to all aspects of a Project Life Cycle>

2.2.1.
2.2.2.
2.2.3.

3. PROJECT SUMMARY
3.1. <Briefly summarize the project. Including high-level processes, how the project was approached, new Business Processes implemented, Project
Change Request, etc.>

May 12 2010

PAGE 2 OF 4
Template Version 2.0

Project Closeout

PROJECT CLOSEOUT

4. WORK ESTIMATES
4.1.

<Based on numbers from ITS Time Tracking System, enter hours that were budgeted at the beginning of the project and actual hours that were
charged at the end of the project. Ensure that all ITS resources have updated their time in time tracking before finalizing this document. Also,
include comments including reasons for times that were significantly above or below the hours that were budgeted>

Work Estimates

Budgeted

Actual

Comments

Total

5. OUTSTANDING ISSUES
<List any and all items that may still exist that need to be tracked even after the project is closed.>

5.1. Outstanding issues should be reported to Help Desk and traced via Remedy.

May 12 2010

PAGE 3 OF 4
Template Version 2.0

Project Closeout

PROJECT CLOSEOUT

6. PROJECT CLOSURE APPROVALS

<List of approvers should be the same as the original Scope Statement. Signatures below verify that all deliverables have been implemented to the
satisfaction of approvers.>

The signatures below certify that the Project Manager has met with and reviewed this Project
Closure document with the individuals below indicating that all deliverables above have been
delivered to their satisfaction based on items listed in the Project Completion Criteria section of this
document and this Project can officially be closed.
Name

Role

Signature

Date

Sponsor
Client
Technical Lead
Project Manager

May 12 2010

PAGE 4 OF 4
Template Version 2.0

Project Closeout