Skip to main content
Closure is the last phase of every HERMES project, traditional or agile. It provides a structure for winding the project down in an orderly way.

​
What happens in Closure

  • The outcomes are checked for completeness and completed from a formal point of view.
  • The final project evaluation is reviewed and approved where needed.
  • The outcomes and documentation are handed over to the core organization, for the application, operating and maintenance organization.
  • The documentation of the project is archived according to the filing rules of the core organization.
  • Depending on the scenario, the legacy system is taken out of operation and removed, together with infrastructure no longer needed. Old data is archived or destroyed.
  • The project organization is dissolved. Before that, the team checks whether parts of it can move to the application organization.

​
How Closure ends

The project closure decision is taken. Open items are handed over to the core organization and the application organization, and the project is complete.

​
In Collabase

  • Write the final project evaluation and the lessons learned in Collabase Docs.
  • Move open items to a project of the application organization. A work item can move to another project, including one in another Space. See Tasks.
  • Once the project is closed, the project owner can archive it.
Last modified on September 24, 2026