CHAPTER 10How to Close a TPM Project
We judge ourselves by what we feel capable of doing, while others judge us by what we have already done.
—Henry Wadsworth Longfellow, American poet
We cannot afford to forget any experiences, even the most painful.
—Dag Hammerskjöld, Former Secretary General of the United Nations
CHAPTER LEARNING OBJECTIVES
After reading this chapter, you will be able to:
- Understand the steps needed to effectively close a project
- Develop a formal vs. informal closing strategy
- Identify the components of project documentation
- Conduct a post‐implementation audit
- Explain the significance of each post‐implementation audit question
- Plan for the next version of the solution
Closing a project all too often elicits a sigh of relief on the part of the development team and the client team. The punishment has finally ended, and everyone can return to their normal jobs. There are probably project responsibilities that are behind schedule and waiting for you to get started on them. Is that how you remember project closings? Or do you remember them as celebrations of success?
In the complex project landscape project deliverables often do not meet expected business value and another attempt at improving the accepted solution will be undertaken. The Scope Bank will contain the learning and discovery that had not been acted upon in this project but will become that major input to the next version of the solution.