The Daily Scrum belongs to the Developers
A 15-minute event for the Developers, at the same time and place every working day. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. If the Product Owner or Scrum Master are working on Sprint Backlog items, they participate as Developers.
Why it is like this
Fixing the time and place removes the complexity of scheduling. Fixing the audience is what keeps it a planning session: the moment it is performed for somebody, it becomes a status report and stops changing the plan.
Not to be confused with
A stand-up, a status meeting, or the three questions. The 2020 Guide removed "What did I do yesterday / What will I do today / What is blocking me" — the Developers may use any structure they like, as long as it focuses on progress toward the Sprint Goal.
In practice
A Daily Scrum where each person reports to the Scrum Master in turn and the Sprint Backlog is never touched has the timebox and none of the purpose.
Source: The Scrum Guide, November 2020 (Schwaber & Sutherland) — Daily Scrum. Read on .
The Scrum Guide is published by Ken Schwaber and Jeff Sutherland under CC BY-SA 4.0. These cards are independent commentary written in our own words, not a derivative of the Guide's text. ytyk.org is not affiliated with, endorsed by or licensed by Scrum.org, Scrum Alliance or the Guide's authors.
Odd one out Check yourself
Three of these are in the 2020 Guide's description of the Daily Scrum. Which one was removed in 2020?
Show the answer
Each Developer answers what they did yesterday, will do today, and what is blocking them
The three questions were dropped precisely because teams had turned them into a round-the-room status report. Any structure is allowed; the purpose is fixed.