Definition
Anyone who deals with project management will inevitably encounter the term “Scrum”. Originally, the term “Scrum” is taken from the sport of rugby and translates as “scrummage”.
The “scrummage” from rugby can be transferred to the collaboration and organisation of project teams. Team members meet regularly in groups, coordinate with each other, and work their way forward step by step. In the Scrum method, these are understood as so-called sprints.
The basis of the Scrum process is the Product Backlog. Here the defined requirements for the project are defined and prioritised. Unlike classical project methods, these requirements are by no means rigid, but are continuously adjusted and re-prioritised. This task is taken on by the so-called “Product Owner”.
Starting from the Product Backlog, individual clearly defined tasks are transferred to the Sprint Backlog. These tasks are completed within a specified period of time – called a sprint. It is important that the tasks contained in the Sprint Backlog can no longer be adjusted or changed.
It quickly becomes apparent that the Scrum method serves the goal of channelling complex projects into tangible, orderly paths. Scrum attempts to ensure both order and flexibility.
The Scrum method has its origins in software development, but today it is also used in other creative projects, especially in agencies. Unlike Kanban, Scrum is less suited to so-called routine activities, but is more specialised in the transparent processing of complex projects.