Next: Sprint Review
In this section, we’ll learn all about the Daily Scrum meeting. We will cover: the inputs to the meeting; the goal; who attends; the timebox; the general approach to running the meeting, and the output.
Once a day, the Development Team holds the Daily Scrum meeting. The Goal of this meeting is to inspect and adapt the ongoing work of the Sprint. The timebox is short – 15 minutes – and so it is important for the Development Team to be highly focused during the meeting.
The ScrumMaster has three responsibilities related to the meeting. First, the ScrumMaster ensures that the Development Team has the meeting. Second, the ScrumMaster ensures that others outside of the Development Team do not participate. And third, the ScrumMaster teaches the Development
Team how to keep the meeting within the 15-minute timebox.
This implies that the ScrumMaster does not lead the meeting in a traditional sense. Once the Development Team has mastered the timebox and the meeting is a regular part of the team’s daily work, the ScrumMaster may choose not to attend, or may choose to attend in a purely neutral and
The Daily Scrum meeting is typically held at the same time and place each day to reduce complexity. During the meeting, members of the Development Team explain their progress and plans in three
What did I do yesterday to help the Development Team meet the Sprint Goal?
What will I do today to help the Development Team meet the Sprint Goal?
Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
The inputs to the meeting, then, are the Sprint Goal and the Sprint Backlog, which is the Development Team’s plan for how they will achieve the Sprint Goal.
To maintain the timebox, the Daily Scrum is focused on the transparency and inspect portions of the empirical process. It is critical that the entire Development Team is present to reach that shared understanding.
The adapt portion very often requires the input of only a subset of the Development Team – those involved with the portions of work that need to be adapted that day to meet the Sprint Goal. For this reason, it is common for some set of the Development Team to meet directly after the Daily Scrum has concluded. They discuss how to self-organize around any issues that were raised, adapting the affected portions of the Sprint Backlog.
The Adapted Sprint Backlog is the primary output of the Daily Scrum meeting.
Effective Daily Scrum meetings have several benefits. They Improve communication. They eliminate the need for other meetings. They identify impediments to development for removal. They highlight and promote quick decision making, and, they improve the Development Team’s level of knowledge. Research has shown that effective Daily Scrum meetings have a high correlation with successful implementation of the Scrum Framework.
- Scrum Foundations Course Video Series
- Scrum Foundations Course – Scrum Theory
- Scrum Foundations Course – Scrum Values
- Scrum Foundations Course – Cross Functional and Self-Organizing Teams
- Scrum Foundations Course – Scrum Roles
- Scrum Foundations Course – Scrum Events
- Scrum Foundations Course – Sprint Planning
- Scrum Foundations Course – Daily Scrum
- Scrum Foundations Course – Sprint Review
- Scrum Foundations Course – Sprint Retrospective
- Scrum Foundations Course – Scrum Artifacts
- Scrum Foundations Course – Product Backlog
- Scrum Foundations Course – Product Backlog Refinement
- Scrum Foundations Course – Sprint Backlog
- Scrum Foundations Course – Product Increment and the Definition of Done