> ## 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. # Introduction to HERMES project management > What HERMES 2022 is: the Swiss federal project management method, its publisher, current edition, traditional and agile approach, and where it is used. HERMES is an outcome-oriented project management method for projects of every kind: changes to an organisation, IT systems, services and products, or infrastructure. It gives everyone involved the same structure and the same vocabulary, from the steering committee to the development team. ## Publisher and edition | Item | Details | | ------------------- | -------------------------------------------------------------------------------------------- | | **Publisher** | Swiss Federal Chancellery, Digital Transformation and ICT Steering (DTI) | | **Current edition** | HERMES 2022, 3rd printing (revised), 31.12.2025 | | **Standard** | eCH-0054, maintained by the eCH HERMES group of experts | | **Languages** | German, French, Italian, English | | **Where to get it** | [HERMES online](https://www.hermes.admin.ch/en/), including scenarios and document templates | The 3rd printing changes some terms compared to the first print of 2023. The role formerly called development team is now the **execution organization**, individual scenarios are now **user-defined scenarios**, and the manual no longer speaks of hybrid project management. ## Who uses HERMES HERMES is the standard method in the Swiss Federal Administration. Many cantons, cities and municipalities use it too, as do companies that deliver projects to the public sector. A tender often names HERMES as a requirement for the project organisation and the documentation. ## Traditional and agile HERMES supports two ways of developing the solution: * **Traditional:** the solution is developed phase by phase in Concept, Implementation and Deployment. * **Agile:** the solution is developed iteratively and incrementally in a single phase, Execution. The agile development method itself, for example Scrum, stays a black box inside HERMES. HERMES only defines the outcomes and roles that connect it to project steering and reporting. Both approaches start with **Initiation** and end with **Closure**. The decision for traditional or agile is taken in Initiation and must be justified. ## The method elements | Element | What it is | | ------------- | ----------------------------------------------------------------------------------------- | | **Phases** | The backbone of every project. Milestones mark the start and end of each phase. | | **Scenarios** | Ready-made combinations of modules for a type of project, for example IT development. | | **Modules** | Reusable building blocks. Each groups outcomes and the tasks that produce them. | | **Outcomes** | Documents and states. They are at the centre of HERMES; each outcome has tasks and roles. | | **Tasks** | The work that produces outcomes, including decision tasks that end in a milestone. | | **Roles** | Who is responsible, organised by partner group and hierarchy level. | ## HERMES in Collabase Collabase gives you one place for the project plan, the documents, the registers and the approvals of a HERMES project. You map the phases and milestones in **Projects**, write the outcome documents in **Collabase Docs** from templates, keep the risk and decision registers in **Registry**, and route phase releases through an **Approval** node in **Automation**. Start with the phase model. Go straight to the setup.