Closing project requirements

Riad

There is a process for project closure. The PMBOK gives some guidance on this but you need to tailor the process to suit your project and client needs / requirements.

Requirements for different types of contract might differ especially in terms of deficiencies, payments and handing over so you need to be guided by the contracts term and conditions.

RK

Thanks for providing the discussion.

I think the closing requirements of the project can be flexibly set according to the terms of the contract.

Clients may want a rigorously completed delivery, or they may only want to put together their findings when the budget is exhausted.
Depending on market conditions, some projects may be terminated prematurely, leaving project budgets.

Projects contracted under these conditions will be closed according to their contents.

The requirements for closing a project will be a combination of:

- Contractual requirements with any third-parties, although it is quite possible that a number of procurements might have been formally closed earlier than the closure stage of the overall project
- Organizational PM standards and policies. For example, document archival & retention procedures might be specified in those.
- The PM and team's own tailoring of how they will close the approach. For example, if there is budgetary provision, then a celebration of some kind might be held.

Kiron

As Rami said above ,
you can refer to close project or phase in the PMBOK guide line.
one of the impotent documents that is necessary to prepare is the Lesson learned register. which is the collection of knowledge and experiences gained trough project life cycle.
another important document is the final report of the project , which Provides a summary of the project performance, objectives , and weather business needs achieved or not.