> ## 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 Initiation

> The HERMES Initiation phase: project initiation order, study, solution variants, next steps decision and execution release, and how to run it in Collabase.

Initiation is the first phase of every HERMES project, traditional or agile. It creates a defined starting point: the goals are aligned with the requirements of the core organization, the possible solutions are known, and the way forward is decided.

## What happens in Initiation

* The project sponsor releases the resources for Initiation, based on the **project initiation order**, and assigns the project manager.
* The **study** is prepared: a first situation assessment, goals and rough requirements, the solution variants, and the project and operating risks.
* The **legal basis analysis** and the **protection needs analysis** are prepared alongside the study.
* For each variant, the team documents whether the solution will be developed traditionally or agile. The **next steps** decision is taken.
* If a product or system has to be procured, a **procurement analysis** runs in parallel. HERMES plans procurement as early as Initiation.
* The matching **scenario** is selected and adapted if needed.
* The **project management plan** and the **execution order** are prepared and aligned with the strategies and goals of the core organization. Stakeholder interests are analysed.
* In the agile approach, the team decides whether release milestones are mandatory.

## How Initiation ends

At the end of Initiation, the core organization and the project sponsor decide whether the project continues. If it does, the **execution release** decision is taken and the execution order is signed. Reasons to stop include poor cost-effectiveness, excessive risk, lack of feasibility, legal or political concerns, or a mismatch with the goals of the organization.

## Key outcomes

| Outcome                       | Purpose                                                     |
| ----------------------------- | ----------------------------------------------------------- |
| **Project initiation order**  | Basis for releasing the resources for Initiation            |
| **Study**                     | Situation, goals, requirements, solution variants and risks |
| **Legal basis analysis**      | Legal requirements for the solution                         |
| **Protection needs analysis** | Information security and data protection needs              |
| **Procurement analysis**      | Whether and how to procure                                  |
| **Project management plan**   | How the project is planned and controlled                   |
| **Execution order**           | The signed mandate for the development of the solution      |

## In Collabase

* Write the study, the project management plan and the execution order in [Collabase Docs](/docs/docs/pages), each from a [template](/docs/docs/templates). Version history keeps every state of a document traceable.
* Record the solution variants and the next steps decision in a **Decision** object type in [Registry](/docs/registry/overview).
* Record the risks identified in the study in a **Risk** object type in the same Registry schema.
* Model the next steps and execution release milestones as tasks and route them through an approval. See [Milestones and decisions](/docs/hermes/milestones).