Chapter 7. How to Close a 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 closing strategy

  • Identify the components of project documentation

  • Conduct a post-implementation audit

  • Explain the significance of each post-implementation audit question

Closing a project is all too often 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?

Tools, Templates, and Processes Used to Close a Project

By using the following tools, templates, and processes you can turn a project closing into an ordered and defined process.

  • Acceptance test procedures (ATP)

  • Implementation strategies

  • Project documentation

  • Post-implementation audit

  • Final project report

Writing and Maintaining Client Acceptance Procedures

The worst time to negotiate the completion of a project is at its eleventh hour. If you wait until then, you are at the mercy of the client. ...

Get Effective Project Management: Traditional, Agile, Extreme now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.