What Is a Daily Scrum? Format, Best Practices & Common Mistakes
The daily scrum is a brief, daily ceremony in the Scrum framework — typically 15 minutes — where the development team synchronizes on progress, surfaces blockers, and coordinates the day’s work. It is one of the five Scrum events and a foundational practice in agile software development.
The daily scrum is often confused with a status report: a moment where team members report to a manager or Scrum Master on what they’ve done. That confusion is one of the most common reasons daily scrums fail to deliver value. Properly run, the daily scrum is a peer-to-peer synchronization — the team coordinating with itself, not reporting upward.
The Purpose of the Daily Scrum
The daily scrum serves three interconnected purposes:
Inspect progress — Has the team made enough progress yesterday to meet the sprint goal? Are there signs of risk or delay emerging?
Adapt the plan — Based on yesterday’s reality and today’s priorities, is the team’s plan for the day still the right one?
Identify blockers — Is anything preventing someone from making progress that the team should address immediately?
The Three Standard Questions
Traditionally, each team member answers three questions:
- What did I accomplish since yesterday’s daily scrum?
- What do I plan to work on today?
- What, if anything, is blocking my progress?
These questions are not a formula to be recited mechanically — they’re a structure that ensures the conversation covers what matters. Some teams vary the format while preserving the intent: focusing on the sprint goal rather than individual tasks, or walking the board rather than going person-by-person.
Who Attends the Daily Scrum
The development team owns the daily scrum and drives it. The Scrum Master facilitates and helps remove any blockers raised. The Product Owner may attend to stay informed but should not direct or dominate the conversation. Other stakeholders may observe but should not participate.
This is not a management reporting meeting. If the daily scrum becomes a moment where developers report to leadership, it loses its collaborative purpose and teams stop treating it as their own.
How Long Should It Be?
Fifteen minutes is the Scrum Guide’s recommended timebox — and it works when the team stays focused on coordination, not problem-solving. When a blocker or discussion needs more depth, the right response is to note it (“let’s pick that up after the scrum”) rather than expand the meeting.
The 15-minute constraint is a feature, not a limitation. It forces the team to communicate concisely and take longer conversations offline.
Best Practices for Effective Daily Scrums
Hold it at a consistent time and place — Predictability reduces friction and builds the habit.
Start on time regardless of who is present — Waiting for latecomers rewards late arrival.
Keep it standing — The physical posture signals brevity and urgency.
Focus on the sprint goal, not a task list — The goal is coordination toward the sprint outcome, not an accounting of every task completed.
Take detailed discussions offline — The “parking lot” approach keeps the daily scrum short and respects everyone’s time.
Rotate facilitation — Avoiding a fixed facilitator reinforces that this is a team-owned meeting, not a management touchpoint.
Common Daily Scrum Mistakes
- Reporting to the Scrum Master or manager — Turns a peer coordination into a status meeting
- Going into problem-solving detail — Solving blockers live extends the meeting and excludes people who don’t need to be in that conversation
- Including too many people — Non-team members talking in the daily scrum disrupts the team’s rhythm
- Making attendance optional — When team members skip, coordination gaps emerge
- Never following up on blockers — Naming a blocker and never resolving it erodes trust in the practice
Key Takeaways
The daily scrum is a small ceremony with outsized impact when run well. Fifteen minutes of genuine, peer-driven synchronization — focused on the sprint goal and empowered to surface real blockers — creates the communication rhythm that keeps agile teams moving together rather than working in parallel isolation.