Application with other methods and practices

HERMES defines the outcomes and the general course of the project. However, it does not prescribe which methods and practices must be used to produce the outcomes.

HERMES is thus supplemented by subject-specific methods and practices over the course of the project (see Figure 37). Users, developers, and operators define these and coordinate them with the tasks, outcomes, and roles according to HERMES.

Figure 37: Use of supplementary methods and practices

For the participants, especially in the context of solution development, this gives rise to new dimensions that universalize the applicability and usability of HERMES and still fully accommodate the individual method protagonists. For example, the user can specify that they will use an open source tool for conceptual data modeling, or the developer can employ the agile development method favored in the developer's core organization for the development process.

The following points must be observed when supplementary methods and practices are used:

1. The tasks, outcomes, and roles of project steering and project management are always based on HERMES and cannot be replaced by other methods.
2. The HERMES phase model remains in place.
3. The milestones are set and cannot be changed.
4. Specifications on the use of methods and practices are recorded in the project management plan.