Scrum is a framework for iterative development and implementation of products and services. The concept originally stems from software development, but it is now successfully used in almost all work areas.

A unique feature is that work is done in cross-functional teams with shared accountability for the quality of their work. This results in a considerable change in the understanding of roles compared to traditional projects.

Scrum defines meeting formats that ensure flawless and efficient communication between product owner (who has business responsibility) and implementation team.

Thanks to working in short, strictly defined cycles, Scrum allows to reconcile interim work results on a regular basis with customer needs. Developments that fail to meet market requirements can be omitted in this way.

There are three roles in the Scrum framework:

  1. -

    Scrum Product Owner

    he / she holds business responsibility

  2. -

    Scrum Master

    coach and facilitator of the process

  3. -

    Implementation or realization team

    to 9 people with cross-functional capabilities

  1. The product owner is responsible for the project outcome. He makes decisions on deliverables and their priority. He has commercial responsibility.
  2. The scrum master facilitates all scrum meetings. In addition, he supports the product owner in backlog maintenance as well as the team in working with the scrum method. He is the protector of the process and the scrum structures.
  3. The realization team is responsible for executing the tasks and for their outcome and quality. It can liaise with the product owner regarding setting priorities for the topics. The realization team itself makes the decision how to carry out the tasks and determines how many tasks it wants to carry out during a specific sprint. Accordingly, the team itself is accountable.

Cycles from 1-4 weeks with a daily meeting

The scrum team works in cycles from one to four weeks, the so-called sprints. The sprint begins with sprint planning where the implementation team determines the scope of work that is intended to be done during a particular sprint. At the end of each cycle, the implementation team presents the outcome to the stakeholders or selected customers in the sprint review meeting. In addition, the team itself reviews in regular intervals what went well during the collaboration; this review is called sprint retrospective.

The scrum team meets daily (so-called daily scrum) to agree the work to be done at that particular day. This daily scrum meeting is held always at the same place and at the same time every day. This ensures that everybody knows what the others do and who needs help and that no duplicate work is done.


Requirements arising under scrum may be adjusted to the respective team and the respective business situation.

It is important that the communication structures remain intact and that benefits such as the good exchange between team and product owner or the regular feedback by customers and stakeholders are fully maintained during the review meetings.

Andrea SchmittInnovationstrainerinAm Mittelpfad 24aD 65520 Bad Camberg+49 64 34-905 997+49 175 5196446
Your message
Your data

If you contact me via the contact form, I will store your email address and other data provided in the form. You can find more information in the privacy notice.

This website uses a so-called “Session Cookie“ to save the language version you chose and to secure the contact form. This session cookie is deleted automatically when you quit your browser. If you agree, your consent is saved in another cookie for four weeks. Furthermore we use the statistic tool Matomo which uses another cookie. You can find more information and the possibility to opt-out from Matomo in ourprivacy police.