Closing Out Projects: When 'Done' Means Done

Regardless of the type of project management methodology a project manager employs, all projects conclude with a close out. Closing out a project should not be tricky or confusing but it often is. Universally, what it must always represent is the end of a project manager’s involvement. According to A Guide to the Project Management Body of Knowledge (PMBOK® Guide)—Fourth Edition, the definition of a project is as follows:

Purpose: A project is a temporary endeavor undertaken to create a unique product, service or result. The temporary nature of projects indicates a definite beginning and end.

Ah, the end! That glorious day when we deliver the goods, finish our supervision of the work, we button up the document library, and the project team gets the high fives for a job well done, while you accept the kudos, step out the project door, and move on to new projects.

But is it really that simple? Are you really done? Why then are you receiving all the phone calls and emails? What about those nagging customer tweets? How many of us have closed out a project, joyfully attended the product launch, executed the go-live, moved past the warranty period, and you see your project in production — only to continue to field calls and issues on the product? Are customers calling you, sponsors emailing you? Are you still involved in meetings, post …