A daily standup is a 15-minute timeboxed meeting where the Developers on a Scrum team synchronize work and surface blockers. That's it. Not a status report to management. Not a chance to show how busy you are. A synchronization.
The Scrum Guide calls it the Daily Scrum. Same thing. Happens every working day at the same time and place (or video link). The Developers decide how to structure the conversation, but most teams use three questions: What did I complete yesterday? What will I work on today? What's blocking me?
Think of it like a pilot's preflight check. Quick. Structured. Focused on what could go wrong.
Where This Came From
The daily standup emerged from XP (Extreme Programming) teams in the late 1990s who needed a way to stay coordinated without endless email threads or status meetings. Ken Schwaber and Jeff Sutherland incorporated it into Scrum because distributed knowledge kills teams. If one person knows the blockers and another doesn't, you're not a team yet.
The 15-minute timebox is non-negotiable in Scrum. It's not a suggestion. When teams ignore the timebox, standups bloat into planning sessions or problem-solving workshops. Then they stop happening, or people start skipping them.
How It Shows Up in Practice
On Monday morning at 9:30 a.m., your team gathers (in person or on Zoom). Everyone stands (hence "standup"). The Scrum Master keeps time. Each Developer speaks for roughly 2-3 minutes. No tangents. No solving problems on the clock.
When someone says "I'm blocked waiting for the API from the other team," that's a flag. The Scrum Master notes it. After standup, they own clearing it. That's the Scrum Master's job: remove what's in the way so Developers can do their work.
The Product Owner can attend but doesn't speak unless asked a clarifying question. They're there to listen and stay informed, not to reprioritize mid-sprint based on what they hear.
Remote teams need one rule: everyone on video, camera on. A mix of in-person and remote people on a call creates a two-tier team dynamic. It doesn't work.
What People Get Wrong
Most teams treat standup like a status report to the Scrum Master. "I finished the login form. I'm starting the password reset. No blockers." That's theater. The Scrum Master doesn't need to hear it. The other Developers need to hear it, because they might depend on the login form or have a solution for a blocker.
Another mistake: solving problems in standup. Someone says they're blocked. The team immediately brainstorms for 10 minutes. Now you're 25 minutes in and other people are disengaged. The rule is simple: surface the blocker, name the owner, solve it offline.
Third mistake: skipping standups when the sprint is "going well." Standups aren't about problems only. They're about alignment. If you skip them, you lose the signal that tells you when alignment is breaking down.
Common Pitfalls and How to Fix Them
Standup becomes a status meeting. The Scrum Master is asking each person "what did you do?" like a manager in a one-on-one. Fix: Developers run the meeting. Scrum Master facilitates and timeboxes. If someone's update doesn't matter to the team, they don't say it.
People are checked out. You notice half the team is looking at their phones. They're not engaged because standup feels like theater. Fix: Make it matter. When a blocker surfaces, actually clear it. When someone says they're stuck, the team leans in. Standup becomes the place where real problems get named.
Remote teams have a two-tier dynamic. Three people in the conference room, two on Zoom. The in-person people talk to each other; the remote people are ghosts. Fix: Everyone on video, even if you're all in the same office. Leveled playing field.
Standup drifts into planning. "We should probably pair on that feature." "Yeah, let's figure out the architecture." Now you're 20 minutes in. Fix: Timebox ruthlessly. When someone tries to solve a problem, interrupt. "That's a great question. Let's take it offline and come back with a plan."
Distributed teams across time zones. You can't get everyone in one meeting. Fix: Split into regional standups if you have to, but have a written sync afterward so people in other zones know what happened. Or record it. The point is that information flows.
Measuring Whether Standup Is Working
Don't measure standup by attendance or how quickly people finish talking. Measure it by whether blockers actually get cleared.
After a month of standups, ask: How many blockers surfaced in standup? How many got resolved within 24 hours? If the answer is "we named 12 blockers and cleared 2," your standup is broken. Either the Scrum Master isn't owning the removal work, or the blockers are structural and need a sprint retro conversation.
Another signal: Do people come to standup with a plan for the day, or are they making it up as they speak? If people are winging it, they're not thinking about their work in relation to the sprint goal. That's a refinement or sprint planning problem, not a standup problem, but standup will show you it's broken.
After your first Certified Scrum Master (CSM) training, you'll run standups differently. You'll see what a functioning one feels like. Our instructors, including Giora Morein (a Certified Scrum Trainer who's trained 45,000+ professionals), will show you the rhythm. It's not complicated, but it's easy to drift.
Distributed Teams and Asynchronous Alternatives
Some teams try to run async standups: everyone posts their update in Slack, no meeting. It works for some contexts. You don't burn 15 minutes in a meeting.
But you lose the real-time conversation. If someone says they're blocked, you don't see the face of the person who knows the answer. You don't get the quick clarifying question that unblocks them in 30 seconds. Async standups tend to become status dumps that no one reads.
If your team is spread across four time zones and a synchronous standup is impossible, async is better than nothing. But it's a workaround, not ideal. The Scrum Guide assumes a co-located or time-zone-compatible team for this reason.
How Standup Connects to the Rest of Scrum
The Daily Scrum is one of five ceremonies in Scrum. It's not isolated. If your sprint planning is weak, standup will be chaotic because people don't have clear work. If your backlog refinement is weak, standup will surface confused stories mid-sprint. If your retrospective isn't working, you'll keep making the same standup mistakes every sprint.
Standup is the daily pulse. It tells you whether the other ceremonies are working. Pay attention to what standup shows you.
If you're running a team and want to understand how standup fits into the full Scrum framework, consider our Certified Scrum Master certification or team coaching. We teach the ceremonies as a system, not in isolation. You can also explore what Scrum training actually covers to see if it's the right fit.
The 15-Minute Rule Is Not Flexible
Teams often ask: "Can we do 20 minutes? We have 12 people." No. If you have 12 people, your team is too big. Scrum recommends 3-9 Developers. If you're bigger, split into multiple Scrum teams.
If your standup keeps running over 15 minutes, one of three things is true: (1) You're solving problems instead of surfacing them. (2) Your sprint planning didn't give people clear work. (3) Your team is too big.
Fix the root cause, not the symptom. Don't just accept 25-minute standups as normal.
Getting Started This Week
If your standups are broken, pick one thing to change next week. Not everything at once.
Maybe it's: Developers run the meeting, not the Scrum Master. Or: When a blocker surfaces, name the owner and stop talking about it. Or: Everyone on video, no hybrid. One change. See what shifts.
Related Resources
- Considering how certifications impact your career? See ITIL Certification Fees: What You'll Actually Pay.
- To further develop your team's expertise beyond the daily standup, explore our guide to Scrum Certifications.
One short email, every other Friday. Real-world Scrum lessons, no fluff. Unsubscribe anytime.