Integration of HERMES into the core organization

General

Since each core organization has its own specific characteristics, it is often essential and advantageous to adapt the method to its needs to ensure efficient project management.

The following objectives are pursued with the integration of HERMES into the core organization:

  1. Specific core organization processes and requirements that HERMES is not aware of are taken into account.
  2. The project manager, the user representative, and other project participants receive even better support. They have a framework defined specifically for the organization.
  3. Project management efficiency is increased, given that processes and requirements do not have to be reinvented for every project.
  4. Quality is increased with the more extensive integration of practices into the method, of other methods, and of tools. In particular, the widely used agile development methods are deprived of their project management deficits. Thanks to HERMES, they fully adapt to the organization.
  5. HERMES training can incorporate organization-specific adaptations and accordingly be more effective. With regard to certification, it is recommended in particular not to change the HERMES terminology excessively.

Procedure

HERMES is best integrated into the core organization by way of a project.

The project can be carried out on the basis of the service/product adaptation scenario. In doing so, the aspects of the deployment organization are also taken into account in training, and the organization with the processes for operation and further development of project management are created and activated.

The adaptation is made by the project management competence center.

Adapting the method

Integration of important elements into the method

The core organization's requirements are integrated into the method, e.g.

  1. Requirements arising from organization-specific processes
  2. Decision-making process traditional/agile, necessary information for decision-making
  3. Requirements of other decision-making processes
  4. Reporting requirements (project status report, phase report, release report)
  5. Requirements for SLAs, contracts, and agreements
  6. Security and data protection aspects
  7. Aspects of the solution architecture

The specific methods and practices for producing outcomes are integrated into the method, e.g.

  1. Presentation of requirements engineering outcomes
  2. Presentation of data modeling outcomes (e.g. using INTERLIS, UML *Unified Modeling Language (UML), designed by the Object Management Group for object-oriented modeling, is a graphical description language for the presentation of software systems such as database applications, real-time systems, and workflow applications. )
  3. Presentation of business process modeling outcomes (e.g. using BPMN *Business Process Model and Notation (BPMN), designed by the Object Management Group, is a graphical description language for creating business process models, flowcharts, and workflows. )
  4. Embedding of agile development method (e.g. using SCRUM)
  5. Practices for integration into operation (e.g. with the help of ITIL *Information Technology Infrastructure Library (ITIL) is an IT service management framework consisting of best practice processes for the provision of IT services. )

The method components are adapted if necessary. The following points should be observed in the process:

Phases and milestones
  1. The defined phases must not be omitted, but they may be subdivided.
  2. The milestones must not be omitted, but they are guided by the procedure and any subdivision of the phases.
  3. The names of the method components must not be changed.
Outcomes with document templates and tasks
  1. Minimum required documents (outcomes) must not be omitted.
  2. Several individual outcomes can be integrated into a single document.
  3. Outcomes can be split.
  4. Additional outcomes can be defined.
  5. HERMES document templates can be replaced with organization-specific document templates, with document templates from GEVER systems, *Abbreviation of the German “Geschäftsverwaltung”, used in administration for workflow systems with electronic records and process management. or with other solutions.
  6. Outcomes can be described in greater detail in the document template.
  7. Multiple document templates can be created for a single outcome.
  8. Document templates must include the contents defined in the method outcome description, but they can be extended and fleshed out.
  9. The new tasks needed to create the outcomes must be described.
Modules, scenarios
  1. New modules and scenarios can be created.
  2. The defined HERMES scenarios and modules can be extended with outcomes and the associated tasks, but not reduced. If outcomes or tasks are removed from a scenario or module, this results in a customized scenario.
Roles
  1. Roles can be described in greater detail as long as the essential task area is identical.
  2. Further roles can be defined. A role description is mandatory for each new role.
  3. New roles must be assigned to one of the hierarchy levels and a partner group.
  4. Minimum roles to be filled as well as their assignment to the user partner group must not be changed.
Checklists
  1. The contents of all checklists can be freely adapted and expanded.
  2. Checklist components described in decision-making tasks cannot be omitted.
  3. Separate individual checklists can also be defined in addition.

Once the organization-specific adaptations have been made, scenarios are created for projects with the same characteristics.