Index

Daily Standup: A necessity or just a burden for dev teams?

Índice:

You’ve probably heard this (or maybe even agree): 12 out of 10 developers hate the daily standup. And it’s not without reason. What was supposed to be a quick alignment chat often turns into a boring micromanagement session or just a repeat of what’s already on the board.

So, the question arises: is the daily standup even effective? Or is it just another empty agile ritual?

The concept behind the daily standup

On paper, the daily sounds like an amazing tool. Inspired by the “Daily Scrum,” it was popularized by the Scrum Guide and embraced by agile teams worldwide. The idea is simple: a short, daily meeting to align task progress, spot blockers, and keep everyone in the loop.

But in practice, this tool often loses its way. Imagine a meeting where everyone just repeats, “yesterday I did this, today I’m doing that, tomorrow I’ll do this.” Doesn’t sound very productive, does it? That’s why a lot of daily standups end up as just a checklist — and nobody wants that.

The daily standup isn’t just a checklist; it’s about connection

A common pitfall is turning the daily into a checklist of completed and pending tasks. But the real idea is to foster connection within the team, keep everyone aware of what’s happening, and, most importantly, identify roadblocks. So if each member is just reciting what they did yesterday and what they’ll do today, something’s wrong.

Ask yourself: is the daily helping the team solve problems, or is it just a formality? If it’s the latter, maybe it’s time to change the format or even ditch the daily. A well-functioning team beats a team just going through meaningless rituals.

Expectation vs. Reality

The expectation is for the daily to be a time for alignment, a chance to catch problems early, and a way to keep the team synced up. The reality? It often becomes an unfocused meeting that feels like a routine and, in many cases, is ignored by team members.

Truth is, a lot of the info shared during daily standups could be checked on a board or task management tool. If the daily is just about these kinds of updates, is it really adding value? Probably not. So, what can be done to change that?

The secret to a productive daily standup

If you’re leading a team, making the daily successful starts even before the meeting. Use that time to check the team’s board: is there a task that’s been stuck for too long? A pull request no one’s reviewed? Any activity that’s moving way slower than usual? Spotting these issues before the meeting makes a huge difference.

During the meeting, keep your eyes on the board. Visualizing activities helps avoid repetition, and everyone knows where to focus. And remember: if a problem comes up that doesn’t affect the whole team, save it for a quick chat after the daily. This keeps the meeting fast and relevant for everyone involved.

What to do when the daily loses its purpose

The daily standup is a tool for the team, not a ritual to follow blindly. If your daily isn’t adding value, maybe it’s time to rethink how it’s run. Here are a few tips that can help:

  • Focus on the goal: The daily should keep everyone aligned and highlight problems. If it’s not doing that, something’s off.
  • Keep it short and to the point: Try to keep the meeting under 15 minutes. The shorter and more direct, the better. You could even limit each person’s speaking time.
  • Use the board as your guide: Stay focused on the task board. This adds visual context and avoids discussions that stray from the meeting’s purpose.
  • Be flexible: If dailies aren’t working for your team, consider scaling them back. Try meeting two or three times a week and, on other days, use async tools like Slack or Discord for quick updates.

A well-run daily can transform the team

An efficient daily standup is one that brings value, helps the team stay organized, and clears roadblocks. This means knowing when to speak up and when to listen, and, most importantly, having a clear goal for the meeting. Dailies don’t have to be a “necessary evil” — they can and should be a productive, strategic moment.

The key is keeping it focused and understanding that sometimes a short, targeted conversation is better than a long one packed with info no one will remember. Set clear expectations with the team, agree on how the meetings will run, and always question if the format is working. If the daily is becoming more of a problem than a solution, rethink your approach.

Async standups can be an alternative

Not every meeting has to be live. Many teams are adopting async updates. It’s simple: instead of meeting every day, team members share updates in chat or a management tool, keeping everyone informed without disrupting the workflow.

In our team, for example, we have meetings twice a week: one at the start and one at the end. On other days, we use async updates. This keeps the team informed and saves us from meetings that could be handled another way.

So, is the daily really necessary?

The daily standup isn’t a requirement; it’s a tool for the team. If it’s causing more stress than solutions, it might be time to adjust the format. A daily can be powerful when used right, but it has to add value for the team — not just be another item on the to-do list.

If your team doesn’t see the daily as valuable anymore, think about what could be done differently. And remember: agile isn’t about sticking to rules rigidly, but finding what works best for your team

Posted by:
Share:

Automate Code Reviews with AI

Posts relacionados

daily

You’ve probably heard this (or maybe even agree): 12 out of 10 developers hate the daily standup. And it’s not without reason. What was supposed to be a quick alignment

daily

You’ve probably heard this (or maybe even agree): 12 out of 10 developers hate the daily standup. And it’s not without reason. What was supposed to be a quick alignment

daily

You’ve probably heard this (or maybe even agree): 12 out of 10 developers hate the daily standup. And it’s not without reason. What was supposed to be a quick alignment