Daily Scrum Questions: What Teams Should Ask to Keep the Sprint Goal on Track

The right daily Scrum questions help a team understand how work is progressing, where someone needs help, and what needs to happen next to achieve the sprint goal.

Many teams use the classic three questions:

1. What did I do yesterday?
2. What will I do today?
3. What is in my way?

These questions offer a simple way to share updates, but they are not mandatory under the current Scrum Guide. Developers can choose a format that helps them review progress and plan their work for the day.

For example, a team might ask, "Are we still on track to meet our Sprint Goal?" or "Is anyone waiting on something the rest of us can help with?"

These questions shift the conversation away from individual updates and towards the work the team needs to complete together.

Key Highlights of Daily Scrum Questions

• The classic three daily Scrum questions cover yesterday's work, today's plans, and blockers.
• The Scrum Guide does not prescribe a fixed set of questions for the Daily Scrum.
• Effective daily standup questions help teams coordinate work and stay focused on the sprint goal.
• Software, remote, hardware, and marketing teams can adapt their questions to suit their needs.
• Scrum masters help facilitate the meeting without turning it into a status report.
• The Daily Scrum is one of the five Scrum events, a 15-minute event that helps developers decide how to move forward together.

Introduction

A daily scrum can easily become a meeting everyone attends out of habit.

Each person shares what they worked on yesterday, explains what they plan to do today, and mentions a blocker if there is one. Fifteen minutes later, the meeting ends, and everyone gets back to work.

But has the conversation actually helped anyone move forward?

A developer might be waiting for a code review. A tester might be unable to begin because a feature is incomplete. Someone else might have discovered a problem that could put the Sprint Goal at risk. If these concerns never lead to a discussion, the team has shared updates without making much progress.

That's where daily Scrum questions make a difference.

The right question can uncover a dependency, reveal a risk, or help two team members realize they need to work together. Instead of simply describing what they have been doing, people begin discussing what the team needs to achieve.

The familiar three questions are a useful starting point, especially for teams new to Scrum. But they are not a script that needs to be followed word for word every morning.

What matters is whether the conversation helps the team understand its progress and decide what to do next.

What Is the Purpose of the Daily Scrum?

The Daily Scrum is a 15-minute event for the Scrum Developers to inspect their progress toward the Sprint Goal and adapt their plan for the next Sprint as needed.

It happens on every working day of the sprint. The team uses this time to check where things are at, identify dependencies, and work out if anything needs to change.

The purpose of the daily Scrum is not to give the Scrum Master a daily report. It is to help developers coordinate their work and make decisions that bring them closer to the sprint goal.

Say a team is working on a payment feature. One developer has completed the payment screen, another is working on the API, and the third is preparing the tests..

Everyone might report that their work is progressing. But a conversation about the actual goal could reveal that the API response has changed, the payment screen needs an update, and testing cannot begin until the two components work together.

Now the team has something useful to act on.

If you want a broader explanation of the event, this guide on what is a daily Scrum explains how it fits into the Scrum framework.

The Classic Three Daily Scrum Questions

The traditional three questions have stuck around for a reason. They are simple, familiar, and help teams cover progress, plans, and obstacles without spending too much time on updates.

What Did I Do Yesterday

This question gives team members a chance to share what has changed since the last Daily Scrum.

A developer might say they finished the login validation logic but found a problem with password recovery.

That is a useful update. It becomes even more valuable when the developer explains how the issue affects the team's progress.

For instance, the login feature is ready for testing, but the password recovery problem needs to be fixed before the team can test the entire flow.

Now everyone understands both the progress and the remaining work.

The idea is not to list every activity from the previous day. It is to share what the team needs to know to move forward.

What Will I Do Today

This question helps team members share their immediate plans and see opportunities for coordination.

So, one developer will integrate an API and the other will write tests. If they share their plans, they can figure out when the integration has to be ready and if they should work together.

The conversation may also show that two tasks depend on the same person or resource. Then the team can discuss how to work around that dependency before it becomes a delay.

A useful answer connects today's work to the Sprint Goal rather than simply naming the next task on someone's list.

What Is in My Way

This question gives people room to raise problems before they become bigger issues.

A blocker might be missing access credentials, an unanswered question, a delayed code review, or a dependency on another team.

Take a developer who cannot continue until a stakeholder clarifies a requirement. If the team learns about this early, someone can follow up, and the developer can decide whether there is other useful work to pick up.

Not every obstacle needs to be solved during the meeting. Sometimes, identifying the problem and agreeing on who will handle it is enough.

These three questions provide a helpful structure, but they are not the only way to run a daily scrum.

Why the Three Questions Are No Longer Mandatory

In the current Scrum Guide (published November 2020), teams don’t have to use the classic three questions.

Instead, it gives developers the freedom to choose their own structures and techniques. The daily scrum should still focus on progress toward the sprint goal and produce an actionable plan for the next working day.

This flexibility matters because a team’s needs change in the course of a sprint.

A team getting ready for a release might think about testing and quality risks. Another might be struggling with dependencies between developers. A team dealing with changing requirements may need to rethink its immediate priorities.

Asking everyone the same questions every day can sometimes get in the way of those conversations.

The three questions are not wrong. They simply are not the whole picture. This Scrum.org post on why the three questions won’t die makes the same point.

Good daily Scrum meeting questions reflect what is happening in the team right now. They help people share useful information, raise concerns, and agree on the next steps.

Better Daily Scrum Questions Centered on the Sprint Goal

Teams do not need to ask every question on a long checklist. A few relevant prompts can be enough to get a useful conversation started.

Progress Questions

These questions help the team understand whether its work is moving towards the sprint goal.

• What progress have we made towards the Sprint Goal?
• Has anything happened since the last daily scrum?
• What needs to occur before we can deliver the desired outcome?”
• Are we still on track for the Sprint Goal?
• Should we change our plans for today?

Picture a team that has finished a few development tasks but hasn’t tested the main feature yet. By asking about the sprint goal, the team understands that the fact that the tasks are done does not mean that the intended result is almost ready.

Collaboration Questions

Sometimes, people make better progress by working together than by continuing with separate tasks.

These daily standup questions can help:

• Who needs help moving their work forward?
• Is anyone waiting on another team member?
• Is there something we could complete together today?
• Are we waiting for a review, decision, or handoff?
• Would pairing or sharing knowledge help us make progress?

For example, a developer might finish an API that another team member does not yet understand. Rather than letting the work sit, they could spend some time pairing and get the integration moving.

The aim is to make collaboration easier, not create more meetings.

Risk and Blocker Questions

When people fail to raise problems when they’re small, they can become big delays.

These questions help the team to catch trouble before it grows:

• What is stopping us from achieving the Sprint Goal?
• Have new dependencies emerged?
• Are we waiting for information or access?
• Is there a quality issue that could hold up delivery?
• What needs attention as soon as this meeting is over?

Suppose a team is waiting for approval from another department. Instead of simply mentioning the delay, the team can decide who will follow up, when a response is needed, and whether there is another way to move forward.

That gives everyone a clearer next step.

Daily Scrum Question Examples by Team Type

The most useful questions depend on the work a team does. A software team might be dealing with integration issues, while a marketing team could be waiting for content approvals.

A software team might use these questions to coordinate development and testing. A remote team may need to plan handoffs before colleagues in another time zone finish their day.

For a hardware team, component availability or laboratory access could be the main concern. A marketing team, meanwhile, might need to resolve a delayed design approval before a campaign can launch.

The point is to ask questions that reflect the team's real challenges, rather than follow a template simply because it is available.

Daily Scrum Questions for Remote and Hybrid Teams

Remote and hybrid teams often have fewer chances to resolve small questions through casual conversations. A delayed reply or unclear handoff can leave someone waiting for hours.

A few adjustments can help make the meeting more useful.

• Keep work visible. A shared sprint backlog or digital board lets everyone see what is happening without listening to a long list of updates.
• Make space for different voices. Some people speak up immediately, while others need time to think. The Scrum Master can help ensure that quieter team members have a chance to raise concerns.
• Be specific about blockers. Instead of saying, "I'm waiting on someone," explain what is needed, who can help, and when it is required.
• Use asynchronous updates wisely. Routine information can go into a team channel before the meeting, so agree in your working agreements which updates go there.  Save the live discussion for decisions, dependencies, and changes to the plan.
• Respect time zones. Plan handoffs carefully and avoid relying on the same person to resolve issues outside their normal working hours.

The goal is not to make remote daily scrums longer. It is to make the time count.

How a Scrum Master Facilitates Without Taking Over

The Scrum Master helps the team understand the purpose of the Daily Scrum and supports effective facilitation. However, the event belongs to the developers.

A common mistake is for the Scrum Master to ask every question, collect every update, and decide what each person should do next. Before long, the team is reporting to the Scrum Master instead of coordinating with one another.

A better approach is to help the team take ownership of the conversation.

The Scrum Master can ask whether the team is making progress towards the sprint goal, encourage people to offer help when someone is stuck, and help bring attention to dependencies that need resolving.

If two developers disagree about an integration approach, the Scrum Master does not automatically need to decide who is right. They can help the team identify what needs clarification and arrange a focused discussion after the daily scrum.

It is also worth being aware of common Scrum Master anti-patterns, such as turning the event into a status report or making the team dependent on the Scrum Master for every decision.

Professionals looking to strengthen their facilitation skills can explore Certified ScrumMaster training or Advanced Certified ScrumMaster training.

When the Daily Scrum Turns Into a Status Report

A Daily Scrum has probably become a status meeting when everyone directs their updates to the scrum master rather than to one another.

Other signs include repeating information that is already on the task board, mentioning blockers without following up, and ending the meeting without a clear plan.

When this happens, bring the conversation back to the sprint goal.

Ask what needs to happen next, where someone needs help, and whether anything has changed in the team's plan.

It also helps to remind the team why the meeting exists. A Sprint in Scrum is a focused period for creating a valuable increment, and the daily scrum helps developers coordinate their work towards the sprint goal.

The meeting should help the team make progress, not simply prove that everyone has been busy.

Common Daily Scrum Mistakes

1. Asking the same questions without thinking. The classic three questions are useful, but the team may need a different conversation depending on the day's challenges.

2. Focusing only on individual tasks. Someone can finish several tasks while the overall sprint goal remains at risk.

3. Solving every problem during the meeting. Identify the issue, agree on the next step, and continue detailed troubleshooting with the people involved afterward.

4. Treating blockers as personal failures. People should feel comfortable raising concerns before they become serious problems.

5. Letting the Scrum Master dominate. Developers should lead the discussion and decide how to organize their work.

6. Ignoring changes in priorities or dependencies. When new information changes the situation, the team should be willing to adapt its plan.

Conclusion

Good daily Scrum questions do more than help people share updates. They help a team understand where it stands, where it needs support, and what it should focus on next.

The classic three questions remain a useful starting point, but teams do not have to follow them every day. They can adapt their questions to the work at hand, whether they are dealing with technical dependencies, release risks, or delayed decisions.

For Scrum Masters, the challenge is to guide the conversation without taking it over. Give people room to raise concerns, encourage them to work through problems together, and make sure the discussion leads to a practical plan.

When the questions are relevant and the answers lead to action, the Daily Scrum becomes a useful part of the team's day rather than another meeting to get through.