Project Closure Checklist - Project Management Portal - UW Information Technology Wiki Page 1 of 2

Project Closure Checklist

Added by Kerry Lamb, last edited by Peggy Ross on Jan 27, 2012

To use this template for your project, click on Tools and choose Copy or Export.
View Template Examples of this template. Task Status, Completion Date, Issues, Etc.

1. Hold a lessons learned review with the project team, customer, vendors and management. See Lessons Learned Summary. Focus on situations and processes, not on personalities (the intent is to evaluate the project and not individual performance). Consider what went well (things we want to keep doing) and what could have gone better (opportunities for improvement). 2. Review lessons learned and highlight best practices. The goal is to improve future projects. 3. Prepare a project closure report; include accomplishments (vs. project charter), actuals vs. estimates (e.g., budget and schedule), outstanding issues and risks, staff release plan, lessons learned, deliverables, and any follow-on tasks or phases. 4. Provide performance feedback to staff and administrative managers. 5. Clear out code/document change control repositories (notify team, check in all correct versions, remove non-current versions, archive reusable sources and documents). 6. Clean up development environment (notify team, save reusable items, purge project test space, objects, databases, files and data). 7. Package problem reports (update statuses, dump a report, migrate outstanding problems to production support problem tracking database). 8. Close out testing (package reusable data, tools and documentation; remove debugging or test code from production and development). 9. Retire mailing lists (dump mailing list archives to a folder if needed, request deletion: https://www.washington.edu/computing/forms/mailman/delete.php) 10. Close out project documentation as defined in the records retention plan: Migrate production support items (documentation, reusable tools, data, etc.) to production support team (from folders, change control repositories, web pages; see tasks 5 through 8). Verify that to-be-retained documents are stored in your project's defined location for retained records (migrate from folders, change control repositories, web pages, mailing lists, email). Dispose of to-be-disposed documents. 11. Remove project web site, folders, project shares, etc. 12. Restore normal security & access; delete project-specific nebula groups. 13. Follow any other organizational project closeout procedures (e.g., close CacTrack project).

https://wiki.cac.washington.edu/display/pmportal/Project+Closure+Checklist

10/12/2012

Project Closure Checklist - Project Management Portal - UW Information Technology Wiki Page 2 of 2

Labels: project

closure

checklist

template

1 Comment
Elizabeth Runkle Notify project partners of completion, and include maintenance contacts. Jul 08, 2008

Printed by Atlassian Confluence 4.1.9, the Enterprise Wiki.

Ask a question or get help

https://wiki.cac.washington.edu/display/pmportal/Project+Closure+Checklist

10/12/2012