Implementation units and releases
If a project is to deliver initial outcomes for productive use as quickly as possible, or if the overall complexity is too high to allow the entire scope to be implemented at once, implementation and deployment can be broken down into several implementation units.
The implementation unit comprises all of the technical and organizational outcomes required for deployment and utilization.
In IT projects, the IT system is often implemented with software releases that are continuously tested and integrated. An implementation unit can be developed with several releases.
Implementation units and releases are defined as follows:Implementation unit
An implementation unit (IU) comprises all of the technical and organizational outcomes of the project that are necessary for the system or parts of it to be put into operation. The product or system is used productively at the end of an implementation unit.Release
A release is an outcome which constitutes an operational IT system. The release does not necessarily have to be put into operation by the user, and can instead be delivered in the form of a test object.
Implementation units and phase model
The HERMES phase model enables both the sequential and parallel development of implementation units. Each implementation unit covers the implementation and deployment phases. Before the start of the first implementation unit is released, the concept phase is completed.
Figure 30 shows the time lag for the implementation and deployment of two implementation units. Several releases are developed within an implementation unit.
In the case of implementation units, the following points need to be observed:
The initiation and concept phases are completed. Implementation units can be started after the concept phase. After that point, the project takes place in the phases and milestones of the respective implementation unit. There is no superordinate phase model.
Although the number of implementation units is not limited by HERMES, the duration of the project should not be unlimited. For this reason, the implementation units are planned as a whole in the concept phase.
Each implementation unit covers the implementation and deployment phases. Each implementation unit goes through the decision tasks of steering, management and execution.
The start of an implementation unit must be released by project steering. This requires an updated project management plan.
From a controlling perspective, implementation units are planned and controlled separately in terms of costs, deadlines, and outcomes. They form independent control units. Accordingly, reporting should be geared to the implementation units.
For logical reasons, a final evaluation of the implementation unit is carried out at the end of every implementation unit and the lessons learnt are documented and used.
At the end of the last implementation unit, the project is closed with the corresponding tasks and outcomes. This includes the final project evaluation of all implementation units.