Daily Scrum
A 15-minute, timeboxed event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog.
What it means
The Daily Scrum happens every working day of the Sprint at the same time and place to reduce complexity. It is an internal planning event for the Developers, not a status report to the Scrum Master or Product Owner.
The Scrum Guide does not prescribe a specific format such as 'yesterday, today, blockers'; teams can choose any structure that helps them create an actionable plan for the next day of work.
Common mistakes
Improving communication, eliminating other meetings, identifying impediments, and highlighting decisions are all valuable side effects, but the core purpose is inspecting progress toward the Sprint Goal.
Example
Instead of round-robin status updates, a team walks its Kanban board right to left each morning, discussing only items close to Done.