Project Closure

Project Closure

1. Definition of stage

   • See page 29 & 30
   • Closure is a formal part of project management that is best planned at the start of the project along with the other activities. Closure represents the end of the project and is characterised by the closing of the project budget so that no more money can be spent on the project, completing the documentation and administration requirements of the project, including any final payments to contractors and suppliers, and arranging for the release of the project participants. At handover, the finished product is transferred to the care, custody and control of the owner.

2. Completion planning

3. Unwanted termination avoidance

4. Post Operational Evaluation (POE)

5. Implementation of POE

6. Reward and recognition

7. What does the client expect for closure?

8. Why is closure important?

   • Projects, by definition, have a beginning and an end. Without a formal closure process, projects can drag on as stakeholders strive to include ‘just a few more requirements’. These unbudgeted add-ons can create serious consequences like: significant impacts to schedules and budgets; sponsor interest wanes and the team loses motivation and focus. Any significant changes at this stage of a project should be treated as a second release and a new project. These changes have to be tightly controlled by the project manager.
   • As the project manager, you own responsibility to the sponsor, customer, and team to formally close out the project. Being done with the project does not mean being done with the project management process. Merely finishing a project does not ensure that the organization benefits from the project's outcomes. The next steps in the process is to validate the outcomes and formally report the findings.