Back to Overview

Scrum Meetings

Scrum

Daily Scrum (Standup)

Goals
Description

Each day of a sprint, the team holds a daily scrum meeting. These scrum meetings are strictly time-boxed to 10 minutes. This keeps the discussion brisk but relevant. The meetings are conducted standing in order to keep things quick and efficient. All members of the team should be present as this is the most important meeting of the day. If a person works remotely, they can call in remotely using Slack (please organize with TL at least a day in advance and be ready to be called 5 minutes before the meeting).

Rules

Also check out:Standup

Sprint Pre-Definition

Goals
Description

During the Sprint Pre-Definition, backlog items are discussed by the PO and the TL in order to make sure the items are ready to be estimated by the team, i.e. that nothing is missing from the description or resources. After the meeting, the TL breaks down the backlog items into digestible sprint items, i.e. sprint backlog items, which can mean combining or splitting backlog items depending on what makes sense to package together or separate out.

Sprint Review

Goals
Description

During the Sprint Review, the team demonstrates the implemented features to stakeholders such as PO and potentially other departments and individual developers show what cool things they did. The PO gives an overview of the next sprint's priorities and goals so the team can already prepare themselves to what is coming up next.

Sprint Retro

Goals
Description

The sprint retrospective is a meeting during which the team discusses the just-concluded sprint and determines what could be changed that might make the next sprint more productive. It often also helps management to get feedback from the team about the work and progress of project.

Sprint Planning I (SP1)

Goals
Description

In Sprint Planning I, the PO presents his vision for the next sprint. Together with the team he walks through the backlog items and discusses them with the team in order for both sides to understand the requests and clear up potential edge cases early on. The team communicates with the PO in his language (non-technical) about what they see as their concerns and problems. Concrete technical steps for implementation are not discussed yet. The team gives the PO a soft-commitment about what they think will probably be able to fit inside of the sprint which forms the basis of what will then be discussed in SP2.

Also check out: Sprints

Sprint Planning II (SP2)

Goals
Description

TM walk through all items of the backlog they soft-committed themselves to and discuss them on a technical level in order to get a better understanding of the complexity. Then TM compare their capacity with what they want to do and potentially discuss with the PO which items might be removed or added. At the end TM commit themselves before the PO to get all items in the backlog done within two weeks.

Sprint Artifacts