Scrum - a framework for processing complex development tasks by interdisciplinary teams!

What is Scrum?

The central component of Scrum is to derive sub-goals (Sprint Backlog) from an ordered list of requirements for the product (Product Backlog) - defined by the customer via the Product Owner - and to implement these in a fixed time frame (Sprint). This ensures that functional intermediate products/results are developed at short but regular intervals (Increments). The product does not have to be physical, it can also be a new process, a new strategy, factory, warehouse or a even a new organization – almost everything. In the original sense of Scrum this is software.

What roles are there in Scrum?

Stakeholder/Customer

These are the client and all participants/interested parties in the success of the project. They are in contact with the product owner, who takes into account the interests/requirements of the stakeholders.

Product owner

Responsible for the functions and the "economic" success of the product. Detailing and updating the product backlog to fullfill the interests of the stakeholders and determine the order of implementation. Relevant question: What is important?

Development team

Independently evaluates (in terms of content and time) the requirements from the product backlog and divides them into individual tasks. Implementation of the Sprint Backlog to ensure the functionality and quality of the product within the scope of individual increments.

Scrum Master

Ensures compliance with a set of rules (Scrum Framework) to guarantee the success of the project. The Scrum master is not part of the development team, but is responsible as a coach for the process and the removal of obstacles.

Scrum Team

Product Owner, Development Team and Scrum Master form the Scrum Team.

Which events define Scrum?

Sprint Planning

Before a sprint is started, it must be planned. The duration of each sprint should not exceed two hours. There is a learning curve here - it usually takes longer at the beginning. The goal of this planning is to clarify what is to be "developed" in the sprint and how this goal can be achieved. The acceptance criterion is also defined - what is the "definition of done". The result of the sprint planning is the sprint backlog.

Daily Scrum

At the beginning of each working day, the development team meets for a 15-minutes meeting. The aim of the Daily Scrum is to ensure continuous communication and the associated exchange of information about the progress of the work. The Scrum master and product owner are often present at this appointment, but are not actively involved. Thereby 3 questions are asked/answered in a structured way:

- What has been done since the last Daily?

- What has hindered the development (obstacles)?

- What are the tasks until the next Daily?

Sprintreview

At the end of a sprint, the Scrum team reviews the set goals, presents the results and discusses the next steps. The duration of this event is limited to a maximum of one hour per sprint. During the review it is very important that not only the Scrum team but also the customers or users are present, because they can use and validate the functionality of the increment. The feedback of the stakeholders is noted by the product owner and flows directly into the further design of the product backlog.

Sprint retrospective

Also at the end of the sprint the sprint retrospective takes place. At this event only the Scrum team is present and reflects the previous way of working. The goal is to openly address topics, which can be of a professional as well as personal nature. Therefore this event takes place in a "protected" confidential setting. Stakeholders are only allowed to participate in this event upon explicit invitation. The respective improvement measures resulting from the sprint retrospective will be documented and planned. The duration of this event is limited to a maximum of 45 minutes per sprint.

Scrum@BLSG?

In addition to various speeches on the topic of "Agile Project Management in Practice", we have developed a business game to experience Scrum live. Furthermore, our consultants provide support in customer projects as Scrum masters, with technical process expertise. The basis for this is a profound internal training off- and on-the-job in project management as well as the certification as Professional Scrum Master. Philipp Kaiser, Benjamin Greier and Mathieu van Assche are currently completing this certification.