MickyMarvels LLC · Template
🎯

Daily Scrum — 15-Minute Format

The Daily Scrum is the most misunderstood Scrum event. It is NOT a status meeting. Master this guide and run standups that energize the team and protect the Sprint Goal.

15 min
Hard timebox — no exceptions
Daily
Same time, same place
Devs
Who runs it (not the SM)
Sprint Goal
The focus of every update
1

The Three Questions — Focus on the Sprint Goal

1

What did I do yesterday?

What did I accomplish that contributed to the team reaching the Sprint Goal?

✅ "Yesterday I completed the login API endpoint and started unit tests — both directly supporting our Sprint Goal of enabling user authentication."
2

What will I do today?

What am I planning to do today that moves the team closer to the Sprint Goal?

✅ "Today I will finish the unit tests and begin the password reset flow — keeping us on track for the authentication Sprint Goal."
3

Are there any impediments?

Is there anything blocking me or the team from making progress toward the Sprint Goal?

✅ "I am waiting on the design team for the password reset UI mockup — this could delay me if not received by tomorrow morning."

🎯

Notice how each answer connects back to the Sprint Goal. The Daily Scrum is a Sprint Goal progress check — not a report to management. Developers talk TO EACH OTHER about the goal, not to the Scrum Master.

2

Good vs. Poor Daily Scrum

✅ Effective Daily Scrum

  • Developers talk to each other — not the SM
  • Each update connects to the Sprint Goal
  • Blockers are flagged — not solved during standup
  • Finishes in 10–12 minutes
  • Team leaves knowing exactly what to do next
  • SM observes and notes impediments to resolve after
  • Board is updated before the meeting
  • Same time every day — no rescheduling

❌ Ineffective Daily Scrum

  • Everyone reports to the Scrum Master
  • Updates are "I worked on stuff" with no Sprint Goal link
  • Blockers turn into 20-minute problem-solving sessions
  • Runs 30–45 minutes regularly
  • Board is outdated — trust in data is low
  • People skip and send Slack messages instead
  • SM talks more than the developers
  • Cancelled or rescheduled frequently
3

Scrum Master Opening Script

Use this to open the Daily Scrum (first 60 seconds)

SM
"Good morning everyone. Our Sprint Goal is: [state the Sprint Goal clearly]. We have [X] days remaining. Let's check in on where we stand. Who would like to start?"
DEV 1
"Yesterday I [completed task]. Today I will [plan]. [No blockers / I have one blocker: ___]."
SM
[After all updates] "Thank you. I noted [impediment] — let's connect right after for 5 minutes. Anything else that needs to be raised before we close?"
SM
"Great. Based on our burndown, we are [on track / slightly behind / at risk]. [If at risk:] I'd like us to take 10 minutes after this to look at the board together. Everyone good? See you tomorrow."

⏱️

Set a visible timer when the standup starts. When it hits 15 minutes, close the meeting — even if not everyone has spoken. This enforces the timebox. Anything not covered can be handled offline immediately after.

4

Common Daily Scrum Anti-Patterns

The Status Report

Each developer gives a detailed status update to the Scrum Master or manager, who nods and takes notes. Everyone else zones out.

✅ Fix: Remind the team to speak to each other, not the SM. The SM is a facilitator, not a receiver.

The Problem-Solving Session

A blocker is raised and immediately the whole team spends 20 minutes solving it. The standup runs 45 minutes. Nobody is happy.

✅ Fix: Flag the blocker, note it, and explicitly say "Let's take that offline right after — who needs to be in that conversation?"

The Skippers

Half the team sends Slack messages instead of attending. The meeting becomes a report-to-SM session for whoever showed up.

✅ Fix: Coach the team on the value of real-time synchronization. Consider changing the time slot. Investigate if there is a deeper disengagement issue.

The Sprint Goal Disconnect

Nobody mentions the Sprint Goal. Updates are task-level: "I worked on the form" with no connection to what the team is trying to achieve.

✅ Fix: State the Sprint Goal at the start of every standup. Ask: "Does what you worked on yesterday move us toward the goal?"
5

Burndown Check — What to Look For

📉 Healthy Burndown Signs

  • Line trends down consistently each day
  • Remaining work crosses zero by Sprint end
  • Small daily drops — no big sudden drops
  • Team velocity is consistent with past Sprints
  • Scope line is flat — no late additions

🚨 Warning Signs — Act Immediately

  • Line is flat for 2+ days — nothing is completing
  • Line is going UP — scope is being added mid-Sprint
  • Massive drop on day 9 of 10 — work hidden until end
  • No items moved to Done in first half of Sprint
  • Team working on stories not in Sprint Backlog
MickyMarvels LLC
Practical Agile Mentoring · mickymarvels.info