The Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan. Developers choose the structure; the three familiar status questions are not a mandatory script. The Scrum Guide leaves that choice to them.
Keep the goal and the next coordination need together
Open the maintained Sprint Backlog. Ask what changed that affects the goal, then inspect the work and dependencies relevant to that change. Someone's activity may matter, but the purpose of mentioning it is to shape the team's next plan.
Instead of “I worked on the test script,” try “The script is ready for the dataset; we cannot check the goal-related behavior until that input arrives.” That sentence identifies what another person can help resolve.
An illustrative 15-minute structure
Fictional example: the goal, people, times, and work status below are sample inputs. The Sprint Goal is to make the agreed search-quality check repeatable. The script is prepared, but access to the approved dataset is not confirmed.
| Minutes | Inspect or decide | Example output |
|---|---|---|
| 0-2 | What progress or change matters to the Sprint Goal? | The script is prepared; the dataset remains unavailable. |
| 2-7 | What needs coordination to move the goal-related work? | Dataset access needs a response from its owner. |
| 7-12 | How will we adjust today's plan? | Priya contacts the owner; Luis prepares the agreed test cases without substituting unapproved data. |
| 12-15 | What is the next handoff, and what needs a separate discussion? | Priya and Luis reconnect at 11:00; parser debugging moves to an after-meeting follow-up. |
The phase lengths are this team's proposed structure. They add to 15 minutes; they do not prescribe how every Scrum Team must allocate the event.
Name an action instead of repeating the blocker
“Waiting for data” does not identify a next move. The sample coordination note is more specific:
Dependency: Approved dataset access not confirmed.
Next action: Priya asks the dataset owner about access and availability. If no answer is available by the 11:00 check, Priya and Luis discuss what can proceed and what needs further coordination.
Work that can proceed: Luis prepares the agreed test cases. The quality check remains unexecuted until the required input is available.
Backlog adjustment: Record the dependency and today's plan in the maintained Sprint Backlog.
That plan does not promise the dataset will arrive. It gives the team a point at which to inspect the situation again. Do not label the quality check complete because preparatory work is complete.
Separate the short plan from detailed debugging
If Priya and Luis need to inspect a parser error, record an after-meeting follow-up: participants Priya and Luis; purpose inspect the error; input the error record; output a next investigation step. Bring in another person if their knowledge is needed, rather than making every Developer wait for the entire diagnostic discussion.
Put the Sprint Goal, dataset dependency, and today's adjustment together in the reference. Keep the debugging purpose and participants in a separate follow-up note. You can then read the daily plan without confusing a scheduled investigation with progress already made toward the goal.
Prepare a goal-centered agenda
Create a Daily Scrum facilitation reference in US English for Developers.
Sprint Goal: [paste]
Current relevant Sprint Backlog work: [paste]
Observed changes since the last daily inspection: [paste]
Dependencies and blockers: [paste]
Known people available to coordinate: [enter]
Maintained Sprint Backlog location: [enter]
Use a 15-minute total. Suggest a flexible structure for inspecting goal
progress, identifying coordination needs, adjusting the day's plan, and
confirming handoffs. Do not require a round of the three status questions.
Tie proposed changes to the Sprint Goal. For each dependency, identify a
next action, owner or OWNER TO CONFIRM, and reconnection time or TIME TO
CONFIRM. Put detailed debugging in a separate follow-up with purpose,
participants, needed input, and intended output.
Do not invent progress, access permissions, completion, deadlines, or team
agreement. Unknown information stays NOT SUPPLIED. Return a concise text
reference and optional HTML reading version showing the goal and plan
together, with separate after-meeting details. Do not create automatic
reporting, blocker collection, or a duplicate live backlog.
Before the 15 minutes end, read today's adjustment back. The people involved should know what they will coordinate and when they need to look again. Update the maintained Sprint Backlog as needed, then let the smaller follow-up handle the diagnostic detail.
Optional: keep a facilitation reference in NOS
If your team wants an HTML reference while choosing its daily structure, NOS can save and display the goal, coordination prompts, and follow-up distinction. Use that as a preparation aid; daily work and adaptations stay in the maintained Sprint Backlog.