The daily standup is one of the simplest meeting formats in agile, three questions, ten minutes, done. It's also one of the easiest to let drift, into detailed status reports, into live problem-solving that should happen offline, into a meeting that regularly runs to 25 minutes and loses half the team's attention halfway through. This guide covers the standard format, the template, and the specific failure modes that turn a tight standup into a slow one.
The three-question standup format
The classic scrum standup asks every attendee three questions, in order: what did I complete since the last standup, what will I work on before the next one, and is anything blocking me? The format is deliberately narrow. It's not a place to explain how something works, debate an approach, or give a detailed account of a debugging session, those conversations are valuable, but they belong in a separate, smaller follow-up, not in front of the whole team's daily sync. The standup's only job is to make blockers visible fast so they can be resolved before they cost another day.
A free daily standup agenda template
Standup: [Team name] · Time: [Start–end, target 10–15 min] · Attendees: [Names]
For each person, in order:
- What did you complete since the last standup?
- What are you working on until the next one?
- Is anything blocking you?
After everyone has gone: note any blockers raised and who'll follow up on each one, offline, right after the standup ends. Anything that turns into a real discussion (a design decision, a debugging deep-dive) gets parked and scheduled separately, not worked through live in front of the full standup.
Common failure modes (and the fix)
Status reports instead of blockers
When "what did you do yesterday" turns into a detailed walkthrough, the standup slows down for everyone. Fix: redirect explicitly, "quick headline, we can go deeper after if needed", and hold the line consistently until it becomes the norm.
Live problem-solving
A blocker gets raised, and the group starts debugging it together, in front of everyone, live. Fix: acknowledge it, note who'll follow up, and move on, "let's take that offline with [name] right after this."
No one is actually facilitating
Standups without a clear facilitator tend to drift, people talk out of order, tangents go unchecked, and the meeting has no natural close. Fix: rotate a lightweight facilitator role, someone whose only job that day is keeping the format tight.
If your standup consistently runs long despite following the format, the real issue is usually team size, not discipline. Standups work best under 8–9 people; larger teams should split into smaller sub-team standups.
When to run standups async instead
Not every team needs a live daily sync. Teams spread across multiple time zones, or in a steadier phase of work where blockers are rare, often do just as well with an async written standup, each person posts their three answers in a shared channel at a set time, and anyone can flag a blocker for a quick follow-up. This removes the scheduling overhead entirely and gives people time to write a clearer, more considered update than they'd give live. It's a worse fit for fast-moving, high-coordination sprints where real-time blocker visibility matters, but for many teams the async version captures 90% of the value with a fraction of the calendar cost.
Frequently asked questions
The classic scrum standup format asks each person three questions: what did I do yesterday, what will I do today, and what's blocking me? It's designed to surface blockers quickly, not to be a detailed status report. Standups that drift into long explanations of yesterday's work usually run over time and lose the team's attention for the parts that actually matter, the blockers.
For a team of 5–8 people, 10–15 minutes. If your standup regularly runs past 15 minutes, the most common cause is people giving detailed status updates instead of the three-question format, or unblocking discussions happening live instead of being taken offline. Note who's blocked, then follow up with those specific people after the standup ends.
Daily works best for active sprint work where blockers need same-day visibility. Teams in a steadier, less time-pressured phase often do fine with a 2–3x weekly cadence, or an async written standup posted in a shared channel instead of a live daily call. The right frequency depends on how quickly the work changes, not on scrum orthodoxy.
A "daily standup" and a "daily scrum" refer to the same thing, the short daily sync focused on progress and blockers. "Scrum meeting" is sometimes used more broadly to include the other scrum ceremonies (sprint planning, sprint review, retrospective), which are separate, less frequent meetings with different purposes than the daily standup.