Daily Scrum Meeting in Scrum

The Daily Scrum is a short daily meeting that helps the team inspect progress toward the Sprint Goal and adapt its plan for the next day of work.

Done well, it gives team members a shared understanding of what has changed, what is blocked, and what needs attention next. Done poorly, it turns into a status report that people attend because Scrum says they should.

The difference usually comes down to ownership. The Daily Scrum belongs to the Developers. It should help them coordinate their work, not report progress to someone else.

What Is the Daily Scrum?

The Daily Scrum is a 15-minute Scrum meeting held each day of the sprint.

Many teams also call it a daily standup, daily stand-up meeting, or daily huddle. The name matters less than the purpose: the team uses the meeting to inspect progress and adapt its plan.

Most teams hold the Daily Scrum at the same time and place each day. Morning often works well because it helps the team set context for the day. Distributed teams may use video, chat, a shared board, or a combination, but the goal is the same: help the team coordinate around the work of the sprint.

The 15-minute timebox is important. It keeps the conversation focused. The Daily Scrum should be long enough for the team to understand what needs attention, but short enough that it does not become a problem-solving meeting.

The Purpose of the Daily Scrum

The purpose of the Daily Scrum is to help the team inspect and adapt during the sprint.

The team should leave the meeting with a better understanding of:

Progress toward the Sprint Goal
Work that is blocked or at risk
Changes to the team’s plan for the day
Opportunities for team members to help one another
Conversations that need to happen after the meeting

A Daily Scrum is not valuable because everyone talks. It is valuable when the conversation changes what the team does next.

For example, a team might discover that two people are unknowingly working on related problems. Someone may be stuck and need help. A backlog item may be larger than expected. A dependency may be threatening the Sprint Goal. The Daily Scrum gives the team a regular chance to notice these things early enough to respond.

Who Attends the Daily Scrum?

The Daily Scrum is for the Developers on the Scrum Team.

In Scrum, Developers are the people creating the product increment. That can include programmers, testers, analysts, designers, database specialists, UX researchers, writers, or anyone else doing the work needed to create a done increment.

The Scrum Master may attend, especially while the team is still learning to use the meeting well. But the Scrum Master should be careful not to become the person everyone reports to.

The Product Owner may attend when doing so helps the team. For example, the Product Owner may be needed to answer a question, clarify a tradeoff, or hear about a risk to the Sprint Goal. But the Product Owner should not turn the meeting into a review, approval session, or priority debate.

Others may listen if the team finds that useful, but they should not disrupt the meeting. The Daily Scrum is primarily a coordination meeting for the people doing the work.

The Three Questions

Many teams structure the Daily Scrum around three familiar questions:

What did I do yesterday?
What will I do today?
What impediments are in my way?

These questions can work well, especially for teams new to Scrum. They help people keep the conversation short and focused on recent progress, near-term plans, and obstacles.

But the questions are a tool, not a rule.

A team can answer those questions and still have a poor Daily Scrum. That happens when each person reports individually while everyone else waits for a turn to speak. The meeting may be short, but it is not really helping the team coordinate.

The better test is this: does the team leave with a clearer plan for the day?

An Alternative: Walk Through the Work

Some teams get better results by walking through the work instead of walking through each person.

Rather than asking every person to answer the three questions in turn, the team looks at the Sprint Backlog or Scrum board and discusses each product backlog item or important piece of work.

That might sound like this:

What needs to happen for this item to move forward today?
Is anyone blocked?
Do we need to pair or swarm on this?
Is this item still helping us achieve the Sprint Goal?
Is anything at risk of not being done?

This approach often creates a more useful conversation because the team talks about the work, not just individual activity. A person may speak more than once. Some people may say very little on a given day. That is fine if the team gets the coordination it needs.

The Daily Scrum does not need equal airtime. It needs useful coordination.

The Daily Scrum Is a Synchronization Meeting

The Daily Scrum is a synchronization meeting.

Team members use it to align their work: here is what changed, here is what I am doing next, here is where I need help, and here is what may affect the rest of you.

This is different from a status meeting. In a status meeting, people usually report upward to a manager or project lead. In a good Daily Scrum, people talk to one another because their work is connected.

Scrum Masters can accidentally make this worse. If the Scrum Master stands in front of the room, takes notes, asks each person for an update, and maintains eye contact with the speaker, the meeting will naturally drift toward status reporting.

A simple trick helps: the Scrum Master can step back physically and conversationally. Let team members face one another. Let them look at the board. Let them ask each other questions. The meeting should feel like the team is making a plan, not giving a report.

The Daily Scrum Reinforces Team Accountability

A useful Daily Scrum reinforces accountability among team members.

When someone says, “I expect to finish the data storage work today,” that is not a promise to the Scrum Master. It is information for the team. Tomorrow, everyone will know whether that happened and whether the plan needs to change.

That kind of accountability is healthy when it is peer-to-peer and grounded in the team’s shared goal. It helps team members understand how their work affects one another. It also makes progress and problems visible quickly.

The Daily Scrum should not create pressure to sound busy. It should create shared responsibility for making progress toward the Sprint Goal.

What to Do About Impediments

Impediments should be surfaced during the Daily Scrum, but the meeting should not turn into a long problem-solving session.

Common impediments include:

A needed environment, tool, account, or device is not available
Someone needs help debugging a problem
A team member is struggling to learn something and could use pairing
Another group is not responding
A vendor or support group is blocking progress
An approval, contract, or access request is stuck
A leader has asked someone to work on something outside the sprint
The team has discovered unexpected complexity in a backlog item

Naming impediments helps only when something happens next.

Some impediments can be solved by team members immediately after the Daily Scrum. Others need help from the Scrum Master. And some require the Product Owner or a leader to make a tradeoff.

The Scrum Master does not need to solve every impediment personally. But the Scrum Master should help ensure impediments are not ignored, especially when they are outside the team’s control.

Use the Sixteenth Minute

The Daily Scrum is timeboxed to 15 minutes. That does not mean every useful conversation must end when the timebox ends.

If two or three people need to solve a problem, they can stay after the Daily Scrum. Some teams call this the “sixteenth minute.”

This keeps the Daily Scrum focused while still allowing real work to happen. The full team does not need to listen while two people discuss a technical detail. But those two people may need to solve it right away.

A good pattern is:

Surface the issue during the Daily Scrum.
Decide who needs to be involved.
Park the detailed conversation.
Handle it immediately afterward with the right people.

This protects the timebox without avoiding the real issue.

Common Daily Scrum Problems

The Meeting Becomes a Status Report

The most common Daily Scrum problem is that team members report to the Scrum Master instead of coordinating with one another.

You can often spot this by watching body language. If everyone faces the Scrum Master, the meeting is probably drifting. Move the focus back to the team, the Sprint Goal, and the work. For more detail, see Daily Scrums: Synchronization Meetings, Not Status Meetings.

The Team Uses the Three Questions Mechanically

The three questions are useful only when they help the team plan the day.

If the answers become repetitive or shallow, try walking the board instead. Start with the work closest to done. Ask what needs to happen today to move it forward. Then work backward through the rest of the sprint backlog.

The Meeting Turns Into Problem Solving

Some problem solving is tempting because the right people are already together. But once the full team is listening to a conversation only two people need, the Daily Scrum has lost focus.

Use the sixteenth minute. Keep the Daily Scrum short and handle detailed conversations immediately after.

Impediments Are Mentioned but Not Removed

Teams can get discouraged when the same impediments are raised every day and nothing changes.

Track impediments visibly. Decide who will follow up. Revisit whether anything is still blocked. The Daily Scrum should make impediments harder to ignore.

The Sprint Goal Is Ignored

A Daily Scrum that never references the Sprint Goal can become a list of unrelated updates.

The team does not need to say the Sprint Goal aloud every day. But the conversation should be connected to it. If the team is not asking whether today’s plan helps achieve the Sprint Goal, the meeting may be missing its central purpose.

The Product Owner or Manager Takes Over

A Product Owner or manager may ask useful questions, but they should not dominate the meeting.

If the Daily Scrum becomes a place where work is approved, reassigned, or second-guessed, Developers will stop using it as their meeting. The Scrum Master may need to coach observers on how to participate without changing the purpose of the event.

Before You End the Daily Scrum

Before ending the Daily Scrum, the team should be able to answer a few practical questions:

What needs attention today?
What work is blocked or at risk?
Who needs help?
Has anything changed about the team’s plan?
Are we still moving toward the Sprint Goal?
Which conversations should continue after the meeting?

This is not a checklist to read aloud every day. It is a quick way to judge whether the Daily Scrum did its job.

If the team leaves with no better understanding of the day ahead, the meeting needs improvement.

FAQ

Is the daily Scrum only for developers?

Yes. The Daily Scrum is for the Developers on the Scrum Team.

The Scrum Master and Product Owner may attend when their presence helps, but they should not turn the meeting into a status report, review, or approval session.

Does the daily Scrum have to use the three questions?

No. The three questions are common and often useful, but they are not required.

Teams may use the Sprint Goal, Sprint Backlog, Scrum board, or product backlog items to structure the conversation. The format should help the team coordinate and adapt its plan.

Should the daily Scrum be at the same time every day?

Usually, yes. A consistent time reduces scheduling friction and helps the team establish a rhythm.

Morning often works well because it helps the team plan the day, but the best time is the one that helps the team coordinate reliably.

Does the daily Scrum have to be a standup?

No. Standing up can help keep the meeting short, but it is not required.

The important thing is that the meeting stays focused and useful. Distributed teams, teams with accessibility needs, or teams using a board-based discussion may choose another format.

Should the product owner attend the daily Scrum?

The Product Owner may attend when doing so helps the team.

For example, the Product Owner may answer a question, hear about a risk, or clarify a tradeoff. But the Product Owner should avoid taking over the meeting or turning it into a review of the team’s progress.

What should the Scrum Master do during the daily Scrum?

The Scrum Master should help the team learn to use the Daily Scrum effectively.

That may mean observing, coaching, helping remove impediments, or helping the team notice when the meeting has become a status report. The Scrum Master should not run the meeting in a way that makes team members report to the Scrum Master.

What happens if a problem needs more than 15 minutes?

Park the detailed conversation and continue it after the Daily Scrum with the people who need to be involved.

The Daily Scrum should stay short, but important issues should not be ignored. Use the time immediately after the meeting for follow-up conversations.

Last updated July 7th, 2026