The closure phase provides a structure for the systematic shutting down of a project. Project documentation is checked and amended as needed. The project closure is prepared.

1. From the perspective of project management, the closure phase is always handled using the traditional approach. Agile tools can nevertheless also be used.
2. The outcomes are checked for completeness and amended, in particular from a formal perspective.
3. The final project evaluation is checked and approved as appropriate.
4. The project organization is dissolved. Before the dissolution, it can be checked whether parts of the project organization can be transferred analogously to the application organization.
5. The outcomes, documentation, etc., are transferred to the core organization, specifically the application, operating, and maintenance organization. In IT projects, this also applies to the test infrastructure, including the test concept and the tools.
6. The documentation of the project execution, including the outcomes of the approach, is archived according to the filing rules of the core organization.
7. Depending on the scenario and taking the specifications into account, the legacy system is decommissioned and removed, including the old, no longer required infrastructure, and the legacy data is archived or destroyed.

At the end of the closure phase, the project closure is carried out. The final project evaluation is prepared. Open points are transferred to the core organization and the application organization. The project is closed and the project organization is dissolved.