Skip to content
Home » Scrum articles » Daily Scrum

Daily Scrum

The Daily Scrum is an opportunity for the Developers to get together and inspect their progress towards the Sprint Goal. They do this every day, to keep track of their progress and to identify what to do in order to complete the Sprint Goal.

At the Daily Scrum the Developers should answer these questions: How are we doing? Are we on track to deliver the Sprint Goal and complete the work on the Sprint Backlog by the end of the Sprint? Are we late? Do we have impediments that are stopping us from completing the Sprint Goal? What needs to happen today in order to move forward toward the Sprint Goal?

The Daily Scrum is timeboxed to 15 minutes to keep the conversation focused and avoid lengthy discussions.

If the Developers need to sync with each other, talk with the Product Owner, or analyze possible solutions to problems they are facing, they can have these conversations AFTER the Daily Scrum. In fact, the Scrum team works together all day, so besides the Daily Scrum, they have 7 more hours and 45 minutes every day to sync up and discuss solutions.

This means that the 15 minutes at Daily Scrum can be focused on inspecting progress toward the Sprint Goal and updating the plan on what to do today to advance toward completing the work.

The Scrum Master is optional: if the Developers need help facilitating the Daily Scrum, the Scrum Master can support it. For example, the Scrum Master may want to make sure everyone understands the purpose of the event, and the Scrum Master may offer ideas on how to run the meeting. For example, the Scrum Master may offer 3 questions that everyone answers (as examples, choose from those listed above). Or the Scrum Master may suggest to do PBI-by-PBI Review in front of the Sprint Backlog to focus the conversation on the work to be done. In any case, the Scrum Master should not direct the meeting, nor be on the receiving end of the discussion: the Daily Scrum is for the Developers to talk to each other, and no one else.

The Product Owner is also optional: it may be helpful for the Product Owner to listen in and get a sense of how things are going for the Developers, what to expect (or not) by the end of the Sprint, and if the Developers need any help in understanding the scope of work. The Product Owner also should not be on the receiving end of the conversation: the Daily Scrum is for the Developers, and the Product Owner (when present) is a silent observer. Again, any conversation or further discussion with the Product Owner can take place throughout the day, AFTER the Daily Scrum.

Learn more about the Scrum framework with more information on specific events:


Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

Download the Scrum Events PDF

Leave a Reply