Glossary – on the subject of Scrum and Scrumcooking

Agility, the ability to adapt flexibly to changes. This means, for example, not working on a product for months on end in a quiet room, but rather always agreeing on how to proceed during the development process.

Agile software development or the application of agile methods is characterized by several factors: self-organized teams work with minimal design phases. The focus is on rapid implementation and flexible adaptation through regular coordination.

In contrast to simple or even more complicated activities, complex work cannot be broken down into individual work steps, but is: complex. In other words, multi-layered, multi-dimensional, interlocked. With agile project management such as Scrum, complex tasks can be optimally divided into work steps that can be implemented by the project team.

In order not to be distracted during the day by the small flashpoints that tend to capture our attention, it is good to create a daily plan with the most important goals to be achieved that day. See also: Daily Scrum

The team meets every day for the Daily Scrum: 15 minutes, at the same time, in the same place, to briefly update each other and plan further steps.

Status agreed upon by the team that is to be reached in order to be able to consider a development step as completed. Usually includes items such as fully implemented, fully tested, documented, compliant with internal and general standards and guidelines.

Parallel sprint that aims to optimize the print planning: The Focus Sprint is filled with the high-prio stories of the current Sprint until the score is at most equal to the Velocity. In fact, it is better to plan a little below velocity in the beginning. This way, the team can experience how good it feels to successfully and completely complete a Sprint. It is important that there is a clear sprint goal. This simplifies, the selection of stories and enables the completion of larger topic(...)

One of the Scrum artifacts. Describes a concrete stage on the way from the product to the goal. Each increment is a further development of the previous increment, each increment in itself must be usable.

KANBAN (from Japanese: map or board) Like SCRUM, an agile method for process control. Kanban boards usually contain three columns: To do // Doing // Done and are used to visualize processes.

Abbreviation for Large Scale Scrum Framework: The LeSS framework attempts to apply the Scrum method as simply as possible, even in a large corporate context. For this purpose, a new framework is not created, but the Scrum principles are applied to many teams. There is still a single product owner who acts as a liaison between the company and the teams.

(Latin for connection, structure, hub) A method for scaled Scrum for a somewhat larger group of users, such as three to nine teams, working on a common product.

One of the Scrum artifacts. In it, the product owner lists the currently known requirements. The list starts with clear, concrete requirements, but also leaves room for ideas to mature.

Product Owner He/she is responsible for the product. Product here stands for project goal or simply the result.

There are several definitions for this. We like the one of the International Project Management Association best: Project management is concerned with the application of methods, tools, techniques and competencies to a project in order to achieve goals.

Retrospective. Important for determining how the path to a certain point has progressed so far and what conclusions can be drawn for further action. See also: Sprint Retrospective.

Scaled Agile Framework, not a Scrum method, but possibly a good complement to it.

There are several methods to adapt Scrum to the situation in large companies. Scaled Scrum frameworks are for example LeSS, but also Nexus, Scrum of Scrums and SAFe.

SCRUM: An agile method for teams that organize themselves. Project work becomes more efficient and transparent and the product is optimally adapted to the requirements.

Documents in which essential information is recorded: Product Backlog (Product Owner defines Product Goal in it), Sprint Backlog (created by the team, contains info on Sprint Goal), Increment (an operational sub-product that meets the Definition of Done).

Since 2009, there are two organizations that offer Scrum certifications: Scrum.org and Scrum Alliance. Both were founded by the Scrum founders Ken Schwaber and Jeff Sutherland.

By cooking together, a team or a company can get to know the methods of Scrum in an inspiring environment, deepen what has been learned or take it to the next level.

Five "events" that ensure transparency, verifiability and continuous development throughout the process: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.

SCRUM is the most widely used method in agile project management. The term scrum framework here stands for framework, method or also system.

Download the Scrum Guide here: https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-German.pdf

One of the three Scrum roles: The Scrum Master is responsible for the compliance with the Scrum rules and the optimization of Scrum in the company.

An agile method for developing complex products and services. Scrum includes three roles (Product Owner, Scrum Master, Team), five events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective), five values (Courage, Focus, Commitment, Respect and Openness) and three artifacts (Product Backlog, Sprint Backlog, Increment).

Scaled Scrum framework approach in which several individual teams are formed, each of which designates one person to represent the individual team in the SoS meeting. At this meeting, representatives of all teams come together and coordinate the work of their teams with each other.

Next to the Product Owner and the Scrum Master, the third "role" of the Scrum method: The Scrum team is responsible for the creation of the product and observes the Scrum values.

The Scrum Whisk is our lively trademark and logo component. With this essential tool, we manage to let the SCRUM method move from the hand into the brain of our workshop participants 🙂

Our Scrum Workshops are based on Scrum Cooking - a concept developed by Katharina Wirtz to learn the agile project management method Scrum.

The heartbeat of Scrum. A fixed and always constant period of time of maximum 4 weeks, in which a team works on concrete objectives.

The sprint planning session. At the beginning of each sprint run to define the sprint goals.

After each Sprint, the Sprint Retrospective is used to consider what could be done better in future Sprints.

In the Sprint Review, the product increment to be released is reviewed (at the end of each Sprint).

The sprint target does NOT specify what is to be delivered at the end - that is in the sprint backlog. The Sprint Goal provides orientation on what benefit the product increment should have at the end of the Sprint, why it is needed by the client.

Measures to strengthen the cohesion of a team, improve communication, prevent conflicts and strengthen cohesion. Our suggestion for this: Come to SCRUMKITCHEN or let the SCRUMKITCHEN Team come to you!

Velocity can be calculated. In the agile context, it is the amount of work that a team can accomplish during the sprint. Thus, this value plays a key role in the SCRUM framework, because velocity reflects the speed of a team.