> ## Documentation Index
> Fetch the complete documentation index at: https://collabase.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# HERMES phase Execution (agile)

> The HERMES Execution phase in the agile approach: iterations, increments, prioritised solution requirements, optional release milestones and closure phase release.

In the agile approach, Execution replaces Concept, Implementation and Deployment. The variant chosen in Initiation is developed iteratively and incrementally.

## What happens in Execution

* The project organization is set up, including the **execution organization** that develops the solution.
* Situation analyses are carried out, and the requirements from the study become prioritised initial **solution requirements**.
* If business processes or structures are affected, the **organizational requirements** are mandatory.
* If the solution is procured, the tender is carried out, the offers are evaluated, and the product or system is procured.
* Each iteration creates a further part of the solution, the **increment**. Requirements are refined, split and worked through in descending priority.
* Alongside the increments, the organization concept, the operating organization, tests, migration, integration and the deployment concept are developed step by step.
* Preliminary acceptance, deployment measures and the launch of operation are carried out per increment.

HERMES does not prescribe the agile development method. The terms inside the team follow the method you choose, for example Scrum.

## How Execution ends

If the project management plan requires it, a **release** decision is taken before each further release. The **closure phase release** decision is taken, and after the launch of operation and the acceptance of the last release, Execution ends and the execution organization is dissolved.

## In Collabase

* Keep the solution requirements in the [Backlog](/docs/projects/backlog) and plan iterations as [Sprints](/docs/projects/sprints) with story points and burndown.
* If releases need a formal release, model each release milestone as a task and route it through an approval. See [Milestones and decisions](/docs/hermes/milestones).
* Link test runs to a [milestone](/docs/test-management/milestones) per release to see its aggregate pass rate.