The Daily is not a status meeting. It inspects progress toward the Sprint Goal and adapts the plan — and it belongs to the Developers.
Fifteen minutes, every working day of the Sprint, same time and place. The Scrum
Guide is unusually specific about the Daily Scrum, and unusually clear about its
purpose: inspect progress toward the Sprint Goal and adapt the Sprint Backlog as
necessary.
What it is not
The three classic questions — what did I do, what will I do, what is blocking me —
appear nowhere in the current Guide as a requirement. They are one possible structure.
The Guide asks only that the Developers may select whatever structure they like,
as long as it focuses on progress toward the Sprint Goal.
What a good Daily produces
- A focus for today. Not a list of everything in flight — the one or two things
that move the Sprint Goal. - An adapted plan. Something learned yesterday changes what makes sense today.
- Impediments made visible. Not solved in the meeting — named, so they
can be solved right after it.
Keeping it to fifteen minutes
Two habits do almost all the work. Stand up — literally, if you are in a room
together. And when a discussion starts branching, name it and take it after the Daily
with the two people who need it, rather than holding six people hostage to a
conversation that concerns two.
In Agile Together
New tasks that come from that conversation are marked [AI] on the board — and delivering them is exactly what KR4 measures. The impediment block goes to Scrum Events, where it stays visible.
Next
Next: the Definition of Done — what “finished” actually means.
Agile Together is a free course. The package — scripts plus a portable Python — is a single download: get the course package. You install nothing.
Project Together
Track your progress through PMBOK 8
Create your free account to save your reading progress, earn points on every quiz, and unlock certificates as you master each domain.
Create Free Account →Free forever • No credit card required
Project Management