Prepare project closure

Purpose

As part of the preparation for project closure, all final activities and measures are carried out and documented from a formal, organizational, and administrative perspective, open and future pending issues are recorded, and all necessary documents and outcomes are forwarded to the competent bodies so that the decision to dissolve the project organization and terminate the project can be made.

Basic idea

Document storage is purged and the project documentation is transferred to the core organization.

Project execution and the outcomes are evaluated.

All pending items arising from the project are transferred to those responsible in the core organization.

Note:

  1. To review the success of the project, it is necessary (e.g. for the user organization) to check sometime after project closure whether the expected impact has been achieved in the project sponsor's view. This includes an in-depth review of the achievement of objectives or a post calculation, for example.

HERMES-specific

The documentation of the lessons learned is completed. The final project evaluation is compiled.

Basis/prerequisites

Activities

  1. Purge document storage.
  2. Transfer the system documentation relevant for operation, maintenance, and further development to the core organization and archive the project execution documentation (project plans, minutes, contracts, phase reports, etc.) in accordance with the storage regulations of the core organization.
  3. Return unrequired resources (infrastructure, etc.) to the core organization.
  4. Revoke access rights granted specifically for the project.
  5. Finalize expense recording systems, project accounts, reporting, etc.
  6. Compile final project evaluation.
  7. Finalize the lessons learned.
  8. As a pending item, determine what is to be investigated in the context of project success monitoring, what measures are to be envisaged for this purpose, and who is to carry them out.
  9. Transfer all pending items from the project, including necessary measures, to the core organization (e.g. for the attention of the application organization).

Outcomes

Relationships