How Scrum is used

An agile method such as  Scrum is essential for transparency & knowledge transfer within each team. Together with the stakeholders (customer, user, investor, or management), a team's product owner defines a prioritized worklist – the product backlog. The product backlog exists as long as the product lives and can be adapted again and again depending on the market's requirements or the customer. In Sprint Planning, the development team has as many requirements as experience can be in a sprint according to the priority and the sprint goal. In daily meetings, the  Scrum  Dailies, the team coordinates and makes problems and misunderstandings visible within a maximum of 15 minutes.  A sprint, i.e., a kind of work package,  lasts at least one and a maximum of four weeks. During this time, the requirements are implemented so that a potentially deliverable product,  the increment, is created at the end of the day.  The next step, the Sprint Review, introduces the increment to the customer and gets their feedback. This also adjusts the requirements in the product backlog. At the end of a sprint, the team discusses how to improve its working method in the sprint retrospective. Immediately afterward, the next sprint begins with the planning.

The Scrum Master ensures that rules are adhered to, and restrictions are removed throughout the process. According to the self-organization, the development team is responsible for updating all daily tasks in the Sprint Backlog.

Scrum is transparent:  It allows to detect possible problems and delays quickly and early. In this way, knowledge is continuously exchanged in the team. The goal is at the end; the sprint goal is always worked in close work. A minor side effect here is that team members train T-shaped skills. This means that they are experts in their field, but they can also work outside their core area.

SMSgroup Image SMSgroup Image SMSgroup Image SMSgroup Image