The introduction of SCRUM determines how and with what resources agile development takes place. The human, methodological and technical prerequisites are created.

SCRUM is described in the SCRUM Guide™ as "lightweight, simple to understand, difficult to master". For SCRUM to be used successfully, its introduction must be planned and managed throughout.

The introduction of SCRUM has a clear start and a clear end. At the end of the introduction of SCRUM, the achievement of the introduction objectives is checked. If this is not the case, the causes are determined and measures are decided. One possible option is to terminate the introduction of agile development using SCRUM.

The introduction is planned and implemented. First sprints are conducted and experience is gained.

The decision about the system architecture must be made before the start of the actual development.

If development takes place already in the concept phase, this must be planned accordingly and taken into account in the project management plan.

Investments in development during the concept phase (e.g. for the architecture feasibility study) must not result in the phase concept not being completed and implementation largely taking place during the concept phase.

1. Make agreements for the use of SCRUM and record them in the project management plan, e.g.:
2. 1. Length of sprints
   2. Definition of done
   3. Assignment of SCRUM roles
   4. Regulation of change management in HERMES
3. Introduce instruments/tools
4. Establish estimation procedure and estimate outlay
5. Conduct first sprints
6. Gain experience and implement improvements
7. Conduct evaluation after SCRUM has been introduced and decide on the next steps

1. Project management plan