Are daily standups still worth it or do they just hide bigger issues?

Are daily standups still worth it?

Yes. They work. A 15-minute standup lets your team surface blockers, align on sprint goals, and catch dependencies before they become problems. But here's the catch: if you're hearing the same blocker three days in a row, the standup isn't the problem. It's a symptom.

Daily standups are worth it when they do one thing: expose what's actually stuck so you can fix it. They fail when they become a status report nobody listens to.

What makes a standup actually work

A standup that matters has three parts:

• Quick updates (2 minutes max per person). What did you finish? What's next? Done.
• Blocker identification (the real work). What's stopping you? Say it now.
• Follow-up commitment (before you leave). Who's unblocking this, and when?

When standups stick to this, teams move faster. We've trained over 55,000 practitioners since 2001, and the teams that run tight standups spend less time in meetings overall. Counterintuitive, but true.

The trap: standups that drift into problem-solving. You've got 15 minutes. If a blocker needs 20 minutes of discussion, pull three people aside after. Don't burn the whole team's time.

When standups hide bigger problems

If the same blocker repeats across multiple standups, stop and ask why.

Repetitive blockers usually mean one of three things:

• Resource shortage. You're understaffed or the right skills aren't on the team. A standup won't fix that.
• Unclear requirements. The team doesn't know what done looks like. Go back to the Product Owner and the backlog item.
• Team dynamics. Someone's stuck but not saying it. Or dependencies between team members aren't clear. This needs a retrospective, not a standup.

A standup that exposes these issues is doing its job. The mistake is treating the standup as the solution. It's not. It's the diagnostic tool.

When standups might not work

Standups fail when:

• They become a status report to management instead of a team sync.
• Team members show up unprepared or disengaged.
• Nobody acts on identified blockers between standups.
• The team is distributed across time zones and the meeting time works for nobody.

If you're in one of these situations, the fix isn't to kill standups. It's to change how you run them. Some teams shift to async standups (written updates in Slack, reviewed before work starts). Others tighten the time box to 10 minutes. A few move from daily to three times a week if the work doesn't require daily sync.

Your mileage will vary. It depends on your team size, sprint length, and how much work flows between people.

The real question

Don't ask, "Are standups worth it?" Ask, "Is this standup working?" If you're repeating the same blockers, if people are checked out, if nothing changes after you identify a problem, then something's broken. But it's probably not the standup itself.

For more on how teams track progress, check our guide on burn down charts in Scrum. A burn down paired with a tight standup gives you real visibility into sprint health. And if you're running a team that's new to Scrum, our PSM certification covers standup mechanics and when to adapt them.