Why is my Daily Scrum taking more than 15 minutes?

The Daily Scrum is designed to be a focused, 15-minute event that helps teams align and plan their day around the Sprint Goal. Yet for many teams, these meetings stretch far beyond that timeframe, turning into lengthy status updates or design discussions that waste time and drain energy. Why does this happen, and how can it be fixed?

The Problem With “Divide and Conquer”

One common reason Daily Scrums run long is the “divide and conquer” approach to Sprint Planning, where each team member takes on unrelated tasks and works in their own silo. Without a unifying Sprint Goal, there is little reason for the team to collaborate or align their efforts. During the Daily Scrum, this often turns into a long round of individual status updates, with each person reporting their progress in isolation, causing the meeting to drag on well past 15 minutes.

Never miss a post.

Sign up now and receive updates when we post new content.

I will never give away, trade or sell your email address. You can unsubscribe at any time.

The Distraction of Design Discussions

Another reason Daily Scrums can take too long is when they turn into impromptu design sessions. It’s easy to slip into problem-solving mode when someone raises an issue, and others jump in with suggestions and technical details. While collaborating on solutions is valuable, the Daily Scrum is not the time for it, especially if the discussion involves only a few team members while everyone else waits around. These deeper discussions are better handled immediately after the Daily Scrum with the relevant people, keeping the daily check-in short and purposeful.

Lack of a Sprint Goal

Without a clear Sprint Goal, there is no shared direction for the team, making it difficult to measure collective progress and determine what needs to be discussed. The Sprint Goal acts as an anchor, helping the team understand what matters most each day. It keeps conversations focused on what is necessary to achieve the goal, rather than drifting into unrelated updates or off-topic discussions that extend the meeting.

The Value of Visualizations

When teams don’t use visual tools like Scrum boards, burn-down charts, or Kanban boards during the Daily Scrum, meetings often take longer because team members need to verbally share everything about the work in progress. Visualizations allow the team to see the state of the work at a glance, reducing the need for lengthy explanations and repeated questions. A clear, updated board can also prevent unnecessary follow-up questions later in the day since everyone has a shared reference point.

Remember: It’s a Daily Kickstart, Not the Only Planning Moment

Some teams treat the Daily Scrum as the only time during the day to talk about the plan, expecting it to produce a flawless plan for the entire day. This mindset can unnecessarily lengthen the meeting as the team tries to address every possible scenario. Instead, the Daily Scrum should be viewed as a quick alignment to kickstart the day, knowing that plans will adapt as the day progresses and that additional conversations can happen as needed.

Keeping It Short and Effective

To keep the Daily Scrum within its intended 15 minutes:

  • Avoid “divide and conquer” silos; align around a clear Sprint Goal.
  • Postpone design discussions to immediately after the meeting with relevant participants.
  • Use visualizations to reduce lengthy verbal updates and highlight impediments.
  • Treat the Daily Scrum as a starting point for the day, not the only planning moment.

These small but important changes can help teams stay focused, reduce waste, and get the most value from the Daily Scrum while respecting everyone’s time.

Robert Pieper

Robert Pieper has been a licensed Scrum.org Professional Scrum Trainer since 2014 and National Public Speaker since 2013. Robb holds an MBA from Marquette University and an Electrical Engineering Degree from Milwaukee School of Engineering. Robb has 15 years of professional software development experience with a passion for making Scrum work delivering real products and services
Filed Under: , , ,
Tagged with: ,