Daily scrum vs daily stand-up — are they the same?
Daily scrum vs daily stand-up: the same fifteen-minute meeting from two lineages. The Scrum Guide's term, the XP term, and the differences that actually matter.
Daily scrum and daily stand-up are the same meeting. Same fifteen minutes, same purpose, same three-ish beats. The two names come from two different lineages, and the only reason the question keeps getting asked is that people assume two words must mean two things. Here they don’t.
The distinction worth keeping is narrow: “daily scrum” is the term defined in the Scrum Guide; “daily stand-up” is the generic name any team can use. Every daily scrum is a stand-up. Not every stand-up is a daily scrum — because not every team runs Scrum.
Where each name comes from
“Stand-up” is the older word. It comes from Extreme Programming, where the daily stand-up was one of the original practices, and it describes the format literally: you stand, so it stays short.
“Daily scrum” is Scrum’s term for the same meeting, and Scrum gives it a job description. In the Scrum Guide the daily scrum is one of five events, owned by the developers, held at the same time and place each working day, timeboxed to fifteen minutes. Its stated purpose is to inspect progress toward the sprint goal and adapt the plan for the next day’s work.
So the vocabulary maps cleanly:
| Daily stand-up | Daily scrum | |
|---|---|---|
| Origin | Extreme Programming | Scrum |
| Where it’s defined | Convention, not a spec | The Scrum Guide |
| Requires a framework | No | Yes — it’s a Scrum event |
| Owner | The team | The developers |
| Timebox | ~15 minutes | 15 minutes |
| Purpose | Coordinate the day | Inspect and adapt toward the sprint goal |
Read down the two columns and the rows that differ are all context — who defines it, what framework it sits in. The rows that matter for actually running it, timebox and purpose, are the same. That’s why treating them as one meeting is not sloppiness; it’s accurate.
The distinctions that actually matter
If you run Scrum, there are two things the “daily scrum” framing adds that a loose stand-up sometimes loses:
It’s anchored to the sprint goal. The daily scrum isn’t “what did everyone do yesterday.” It’s “are we still on track to meet the sprint goal, and what do we change today if we’re not.” That anchor is what stops the meeting drifting into unstructured status. A stand-up with no goal to steer toward is the one that decays into a task-list read-aloud.
It’s the developers’ meeting. The Scrum Guide is explicit that the daily scrum belongs to the people doing the work. That framing is a defence against the most common way stand-ups go wrong — a manager quietly turning it into a reporting line. The daily scrum is harder to hijack precisely because the spec says whose meeting it is.
Neither of those is unique to Scrum, though. A good Kanban stand-up “walks the board” against the same idea — flow and blockers over individual narration. The framework supplies the discipline; it doesn’t own it.
What to call yours
Use whichever word your team already uses, and don’t correct people who use the other one. If you’re running Scrum, “daily scrum” is technically the right term and it usefully reminds everyone the meeting is anchored to the sprint goal. If you’re not running Scrum, “stand-up” is the honest name and nobody will misunderstand you.
The trap isn’t the vocabulary. It’s assuming that because you’ve named the meeting correctly, you’re running it correctly. You can hold a textbook “daily scrum” every morning and still be running a status meeting — see the three questions and their failure mode and the common anti-patterns for why. The name is the easy part.
For how the daily scrum sits alongside the sprint’s other events, see the agile ceremonies guide and the retro guide’s breakdown of the four Scrum ceremonies. To go the other way — into running the meeting well — start with what a stand-up is for, or return to the complete daily stand-up guide for the full set of chapters.
Frequently asked questions
What is the difference between a daily scrum and a daily stand-up?
In practice, none worth arguing over — they are the same fifteen-minute daily meeting. The names come from different places: “daily scrum” is the term in the Scrum Guide, where the meeting has a specific owner and purpose within Scrum; “daily stand-up” comes from Extreme Programming and is the generic name any team can use, Scrum or not. Every daily scrum is a stand-up; not every stand-up is a daily scrum.
Is a daily stand-up the same as a daily scrum?
Effectively yes. If you run Scrum, your daily stand-up is the daily scrum — the Scrum Guide simply gives it a defined role: the developers inspect progress toward the sprint goal and adapt the plan for the next day. Teams outside Scrum run the identical meeting and call it a stand-up. The mechanics are the same; only the framework and the vocabulary differ.
What is the 3-5-3 rule in Scrum?
It’s a shorthand for the shape of Scrum: 3 roles (product owner, Scrum Master, developers), 5 events (the sprint, sprint planning, the daily scrum, the sprint review, and the sprint retrospective), and 3 artifacts (product backlog, sprint backlog, and the increment). The daily scrum is one of those five events — the only one that happens every day.
Do you have to use Scrum to run a stand-up?
No. The stand-up came from Extreme Programming and works for any team that needs to coordinate daily — Kanban teams, support teams, even non-software teams. Scrum gives the meeting a formal name and a defined purpose, but the practice stands on its own. What matters is the habit of a short, daily, blocker-focused sync, not which framework you file it under.