HERMES 2022 - Classic and agile approach, a good symbiosis?
In my first blog article (HERMES 2022 - What's behind it?), I already pointed out important changes in HERMES 2022.
In the second blog article (HERMES 2022 - Why should I use HERMES 2022?), the use of the new, revised method was critically scrutinized.
One of the most striking changes in the new edition is the symbiosis of the classic and agile project management methods. There is hardly a major project today that does not use agile approaches for certain parts. For me, the hybrid form of project management has been a reality for some time now!
The new phase model: are there now clear distinctions between classic and agile approaches?
HERMES 2022 has integrated the two approaches into a phase model. The so-called "solution development" is now embedded in the initialization and completion phase. The main features of the classic approach have not changed compared to version 5.1. In the agile approach to solution development, Hermes refers to the so-called "implementation". I will take a closer look at this phase in the following section. In principle, the minimum required documents must be created in the same way as the classic approach, but iteratively and incrementally instead of sequentially.
It is important to note that the new "Conclusion" phase is always handled in the "classic" way. This is where the documents are finally reviewed and approved. Finally, the approved documents can be handed over to the master organization. Depending on the selected scenario, legacy systems are also "decommissioned" and the project organization is finally dissolved. Finally, the final project assessment must be created and approved.
Project management and development management, hybrid project management and hybrid development management - what's that?The two terms "hybrid project management and hybrid development management" are new in HERMES 2022. The following definition from HERMES 2022:
- Classic project management supports classic development management.
- hybrid project management supports agile and hybrid development management. It is a combination of classical project management and agile development approach.
The following illustration helps to classify the two terms:
Agile development methods are not project management methods, but development management methods. Because projects under HERMES must meet certain framework conditions from the outset, such as compliance with governance and the smooth embedding of the project in the existing planning and controlling processes of the core organization, pure agile development does not meet these HERMES requirements. This is why agile methods are embedded in a suitable hybrid project management system.
As mentioned at the beginning, projects can, for example, initially be started in the traditional way. Depending on the selected scenario (depending on the project characteristics), implementation takes place with a selected supplier (from procurement) using an agile approach. Here, Hermes 2022 offers solutions in the form of possible "hybrid variants", the so-called "development management hybrid". <pThe illustration below shows two possible "hybrid variants":
Hybrid variant 1: The agile approach takes place in the "realization phase"
Hybrid variant 2: In the "implementation" phase, the concepts and realization are first carried out using the agile approach, while the introduction takes place in the classic way
Agile implementation - how does this work?
Let's now focus on "agile implementation" - what do I mean by this?
The variant selected in the initialization phase is implemented iteratively and incrementally. The project organization is established, including the development team. The solution requirements are broken down further, refined and concretized. The requirements are updated and prioritized and processed in descending order of priority (developed, implemented and put into operation), whereby the priorities are continuously updated and adjusted according to the project findings.
The agile implementation is divided into releases (release 1, release 2, ...release n). Release approvals can optionally be requested. Each release is concluded with a release report. This summarizes the results and decisions of the current release and provides an overview of the work still to be done in the project.
In agile solution development, the schedule for the implementation phase is combined with the (agile) release plan. This release plan specifies the scope of the releases and when operation is activated for each release. It also states whether the (optional) "Make release decision" is prescribed in the project or not. Elaboration and description are provided in the project management plan.How has the "user representative" role been redefined - what is it responsible for, what does it now stand for?The role model in HERMES 2022 has undergone an important change with an agile project organization, which is used during the "Implementation" phase.
As already mentioned, the project organization in HERMES 2022 remains classic in the two phases "Initialization" and "Completion". Nevertheless, it is up to the project team to also use agile techniques/methods in these two phases and for suitable tasks.
.
It can be deduced from the above that the overall responsibility for the project and the achievement of the objectives still lies with the "client" role, regardless of the approach chosen. The project manager also has sole management responsibility, as in HERMES 5.1. However, with the "agile approach" in the "implementation" phase, the project manager may not intervene in the self-organization of the development team.
In HERMES 2022, the role of "user representative" is now prominently positioned in the organization chart. This role now has technical product responsibility, whether in the classic or agile approach. In the agile approach in particular, it acts as an interface to the development team and steers it through the solution requirements. Here, the role of "user representative" can be compared to the role of "product owner" (PO for short) in the Scrum framework.It is easy to see that this has greatly increased the demands on the role of "user representative". We will be happy to prepare you for this demanding role and the application of HERMES 2022. <pWould you like to find out more? We would be happy to show you in a "public" or in your own company seminar what will change with HERMES 2022 - book the HERMES 2022 Foundation or the HERMES 2022 Advanced course now.
We look forward to hearing from you and your feedback!
Project management and development management, hybrid project management and hybrid development management - what's that?
The two terms "hybrid project management and hybrid development management" are new in HERMES 2022. The following definition from HERMES 2022:
- Classic project management supports classic development management.
- hybrid project management supports agile and hybrid development management. It is a combination of classical project management and agile development approach.
The following illustration helps to classify the two terms:
Agile development methods are not project management methods, but development management methods. Because projects under HERMES must meet certain framework conditions from the outset, such as compliance with governance and the smooth embedding of the project in the existing planning and controlling processes of the core organization, pure agile development does not meet these HERMES requirements. This is why agile methods are embedded in a suitable hybrid project management system.
As mentioned at the beginning, projects can, for example, initially be started in the traditional way. Depending on the selected scenario (depending on the project characteristics), implementation takes place with a selected supplier (from procurement) using an agile approach. Here, Hermes 2022 offers solutions in the form of possible "hybrid variants", the so-called "development management hybrid". <pThe illustration below shows two possible "hybrid variants":
Hybrid variant 1: The agile approach takes place in the "realization phase"
Hybrid variant 2: In the "implementation" phase, the concepts and realization are first carried out using the agile approach, while the introduction takes place in the classic way
Agile implementation - how does this work?
Let's now focus on "agile implementation" - what do I mean by this?
The variant selected in the initialization phase is implemented iteratively and incrementally. The project organization is established, including the development team. The solution requirements are broken down further, refined and concretized. The requirements are updated and prioritized and processed in descending order of priority (developed, implemented and put into operation), whereby the priorities are continuously updated and adjusted according to the project findings.
The agile implementation is divided into releases (release 1, release 2, ...release n). Release approvals can optionally be requested. Each release is concluded with a release report. This summarizes the results and decisions of the current release and provides an overview of the work still to be done in the project.
In agile solution development, the schedule for the implementation phase is combined with the (agile) release plan. This release plan specifies the scope of the releases and when operation is activated for each release. It also states whether the (optional) "Make release decision" is prescribed in the project or not. Elaboration and description are provided in the project management plan.