Professional

Daily Scrum: alternatives to facilitate it

Automatic translation · View original

Topic illustration: Daily Scrum: alternatives to facilitate it

A practical investigation into the evolution of the most misunderstood event in Scrum.

More and more teams are running the Daily Scrum as a status report to the Scrum Master or, even worse, to the boss, who uses it to "supervise" the work. Fifteen minutes of individual monologues where each person mechanically recites their tasks while the rest of the team mentally checks out, reviewing their to-do list or their email.

This transformation of the Daily is not just a waste of time; it is a symptom that we have lost sight of the fundamental purpose of the event. The three questions that were used for the Daily (and that the Scrum Guide 2020 removed at the time) served as a guide for teams that were perhaps less experienced. But the existence of these questions did not mean they had to be followed to the letter. Doing so, we ran the risk of turning the Daily into an empty ritual focused on individual reporting instead of collaboration toward the Sprint Goal.

The real purpose: synchronization and adaptation

The Daily exists for a clear purpose: to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as needed. It is not an individual task-tracking meeting, but a moment for the team to synchronize as a unit collaborating toward a common goal.

When it works well, the team:

  • identifies impediments before they become critical blockers,
  • detects collaboration opportunities that arise organically,
  • adjusts its daily plan based on what was learned yesterday,
  • and keeps its focus on value, not on activity.

Ways to facilitate the Daily

1. Walk the board: flow as the protagonist

Instead of each person speaking in turn, the team walks the board from right to left (from "Done" toward "To Do"), discussing each work item in progress. This way:

  • The focus is on the work, not on the people.
  • Bottlenecks are immediately visible.
  • Conversations arise naturally about specific items.
  • Work in progress (WIP) is reduced by making it visible.

When to use it:

It is especially effective in teams working with Kanban or that have high WIP problems. It also works well for remote teams sharing their board on screen.

2. Parking lot + After party: separating synchronization from resolution

If what we want is a quick synchronization, we can achieve it in 15 minutes. Topics that require in-depth discussion are noted in a "parking lot" and addressed immediately afterward in an optional "after party" where only the stakeholders take part. This way:

  • The timebox is respected without cutting off important conversations.
  • Technical depth is possible without boring those who do not need to participate.
  • The Daily stays agile and focused.
  • Important decisions get the space they deserve.

When to use it:

Ideal for teams with technically complex work or when there are members with different specialties.

3. Yesterday's weather + Focus items: prediction based on data

The team reviews metrics from the previous day (completed items, bugs found, Sprint velocity), and then each member declares their focus item for today: the most important item they will work on. In this way:

  • Objective data is combined with personal commitments.
  • Accountability is created without micromanagement.
  • It helps identify patterns and trends.
  • Communication is simplified by limiting it to one main item.

When to use it:

Excellent for teams struggling with predictability or that tend to scatter across multiple tasks.

4. Round Robin of impediments: the anti-pattern turned into a tool

Instead of reporting progress, each person only shares whether they have an impediment or need help. If there are no impediments, they simply say "no blockers" and pass their turn. This way:

  • Time is reduced (usually to 5 to 7 minutes).
  • A culture of asking for help is encouraged.
  • The "theater" of activity reporting is eliminated.
  • The focus shifts to collaboration and unblocking.

When to use it:

Perfect for mature teams with high autonomy, or for Sprints with very clear goals and well-defined work.

5. Asynchronous stand-up + Sync point: the response to distributed work

Team members publish written updates in a tool (Slack, Teams, etc.) within a time window. Then there is an optional 5-minute "sync point" to discuss critical impediments. This means that:

  • time zones and individual work rhythms are respected.
  • a searchable record of updates is created.
  • reflection is allowed before sharing.
  • meeting fatigue is reduced for remote teams.

When to use it:

Essential for globally distributed teams or teams with very flexible schedules. Also useful in organizations with "no-meeting days."

Signs that your Daily needs a change

  • The same people always speak, while others remain silent.
  • The Scrum Master is the one who talks or asks the most questions.
  • It consistently runs beyond 15 minutes.
  • Team members arrive late or look for excuses not to attend.
  • The conversations are about tasks, not about the Sprint Goal.
  • There is no evidence of emerging collaboration after the Daily.
  • The team cannot articulate the value of the Daily when asked.

Implementing the change: a practical guide

Weeks 1-2: diagnosis

Measure the current health of your Daily. You can use simple metrics:

  • Average duration.
  • Number of impediments identified vs. resolved.
  • Active participation (who speaks and how much).
  • Net Promoter Score of the event (ask the team: "Would you recommend our Daily to another team?").

Weeks 3-4: experiment

Choose an alternative format and commit to trying it for one complete Sprint. Whatever format is chosen, set clear rules and make sure everyone understands the "why" behind the change.

Weeks 5-6: adaptation

In the Retrospective, objectively evaluate:

  • Have more impediments been identified?
  • Has collaboration improved?
  • Does the team feel that the time is better invested?
  • Is there greater focus on the Sprint Goal?

Week 7+: iteration

Not every format works for every team. The key is to iterate based on real feedback and concrete metrics, not on personal opinions or preferences.

Beyond the format

The evolution of the Daily Scrum does not end with choosing an alternative format. The most mature teams are experimenting with:

  • AI for pattern analysis: tools that analyze updates and automatically suggest collaborations or identify risks.
  • Real-time flow metrics: dashboards that continuously show the state of the Sprint, making the Daily more strategic.
  • Outcome-oriented Dailies: where the conversation revolves exclusively around value metrics and user feedback.

The report is dead, long live collaboration

The Daily Scrum based on individual reports is a relic of an era when we confused activity with progress and supervision with leadership. The teams that thrive will be those that turn this event into a true catalyst for collaboration and focus.

It is not about following a recipe, but about deeply understanding the purpose of the Daily and having the courage to experiment until you find the format that maximizes value for your specific team. The best Daily is the one your team looks forward to because they know those 15 minutes (or less) will help them have a more productive and focused day.

Next time you find yourself in a Daily that seems like a waste of time, remember: you have alternatives to propose at your next Retrospective.

Have you experimented with alternative Daily formats? What were your results?

Share:

Comments (0)