Scrum is based on the knowledge that most development projects are very
complex. Many requirements can often only roughly be described at the
beginning. Through this method it is possible to realize an improvement
with the help of interim results.
Both planning and specification of the intended results are acquired in
cycles. Quality management happens in regular intervals allowing fast
and easy readjustments.
Scrum can be classified as an agile method following the Agile
- The focus lies on the field of software development.
- Typically Scrum works with boards (see Kanban).
- Every morning there are stand-up meetings.
- Results are gained through a cyclic working method (sprints).
- This method has few roles (product owner, Scrum master, team
- The teams are mixed and have a size between 4 and 8 persons.
- Scrum is remarkable for its simplicity.
- Product owner: provides the technical requirements and prioritizes
- Scrum master: supervises the Scrum process and supports the team
within the Scrum method.
- Team members: collaboratively work through the backlog (works of the
- product backlog
- The product backlog includes all tasks that have to be done.
- sprint planning (planning of the next cycle)
- At first all work packages that have to be completed are defined,
discussed and classified as tasks in the so-called sprint backlog.
- sprint (iteration, cycle of 4 weeks)
- Here the team members work off the tasks of the sprint backlog.
- sprint retrospective
- At the end of a sprint the achieved status is discussed. Not
completed tasks are returned to the product backlog or are part of
the next sprint planning. Furthermore there is a feedback session
about the last sprint.
- daily meeting (stand-up meeting, short meeting daily)
- Every day (morning) the team members meet for a stand-up meeting.
The respective working progress is reported, problems are discussed
and necessary decisions are claimed.
- interim results
- After every sprint a deliverable product (software package) is
Scrum is strongly focused on the processes of software development. This
method assumes the creation of a software product with a manageable
number of tasks (work packages).