An All Purpose Checklist for Project Closure
You’ve reached that point in the project where you stand at deployment and you are ready to shake hands with the project customer and move on to your next assignment. Do you just flip the switch, wave goodbye and ride off into the sunset? Is your job complete? How do you know…what is your yardstick for saying, “that’s it, we’re done here!”?
From my project experience there are some key steps and critical things to check on as the project is deploying so as to ensure that the engagement is over and the solution is ready for the project customer. I’d like I present what I consider to be a reasonable ‘general’ checklist for use at project close out to ensure you’ve dotted the I’s and crossed the T’s before moving on to your next project.
- Are all deliverables delivered?
Review the project schedule closely. Has your project team successfully delivered on all project deliverables? And just as importantly, do you have something documenting customer acceptance of each project deliverable? Is there a formal signoff in your project folder?
Are all invoices current?
Most projects either bill time and materials, by deliverable, or monthly. Look through all project invoices. Has everything that should be paid up till now actually paid? If not, now is the time to check with the customer to see if there are any outstanding invoice issues and work to resolve them quickly.
Has a lessons learned session been conducted or at least scheduled?
I’m a fan of conducting one or more lessons learned sessions before the actual point of deployment because it’s hard to pull everyone together after the solution has been turned over to the customer and to support staff. But if you’ve not held a session yet, schedule that now with the client even if it’s just a one or two hour phone call.
Have all user acceptance testing (UAT) issues been resolved?
How did UAT go? Were there any remaining issues to be fixed? Ensure that those have been acceptably resolved prior to deployment. Make sure that you have a formal UAT signoff in hand as well – a project that does not have a formal testing acceptance from the project client should not be headed for deployment.
Are all training issues completed?
Most customer solutions require some level of training to be conducted for the customer’s end user community. Naturally, this would have been well laid out in the project schedule with specific tasks designed to ensure that this is accomplished. Review the schedule to ensure that all training tasks are complete – a customer who doesn’t know how to use their newly deployed system will likely not be a satisfied customer who gives good references to other potential project clients.
Is a formal project acceptance signoff ready for the customer?
Finally, do you have a formal signoff document ready for the customer to sign upon deployment of the final solution? It’s important that you’ve been accumulating ‘official’ acceptance signoffs on all deliverables up to this point, but this one is probably the most important of all as it signifies overall acceptance of the deployed solution to the customer. Any discussion of remaining outstanding invoices will likely begin and end with this signoff, so make sure that it is always part of your project closure checklist.
This is my practical checklist for closing out a project engagement. Readers – do you have other things that you would suggest adding to this list? What other items do you consider critical to every project to cover before considering the engagement closed out?
Kevin Sequeira is a Product Manager a Tenrox, the leading workflow-driven project management and professional services automation solution.