Project Closure

The final process in a single-phase project is project closure; Multi-phases project also has each phase's closure and will automatically be a trigger for the next phase's initiating process. In the project closure process, a project manager is expected to coordinate with stakeholders and verify the project's documents and deliverable(s) to make sure what has been planned (in planning process) is now materialized and ready for hand-over.

To help the PM in the verification, he/she needs a project management plan to which shows what the expected outcome mentioned during the planning process is/are, the product/service/result itself, and supporting documents for hand-over used in the performing organization. If necessary, a PM might need to assist stakeholders in reviewing the deliverables in detail such as fundamental and technical components, project files and record their feedbacks

Furthermore, in the process, it is important for the PM to get formal acceptance/approval document signed by stakeholders so that they acknowledge/confirm all requirements have been met/completed, and verify that the product/service/result is/are accepted in a timely manner. Aside from the user acceptance, a PM also responsible to update documents and report to Project Management Office (PMO). Those documents include project closure document, product acceptance document, project files archive, and lessons learned. 

After all these legal procedures have been completed, a single-phase project can be labeled completed and the resources initially committed for the project can be released back to resources pool while a multi-phase project is now ready to start the initiating process all over again.

"We expect the closure will have some impacts, but because we draw customers from all along Route 1 and the coast region, we remain optimistic." -- David Fleming