The three questions in the Daily Scrum
“The Developers can select whatever structure and techniques they want, as long as their Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.”
Study — the practice, then what the Guide actually says
What is NOT Scrum
Scrum.org tells candidates to know which agile practices they may have used that are not part of the framework. Each entry: the practice, then what the Guide actually says — or the fact that it says nothing.
Velocity and story points
The Scrum Guide does not mention velocity or story points. It says the Developers who will be doing the work are responsible for the sizing, without naming a unit or technique.
Burn-down charts
“Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism.”
A special case: not part of Scrum, but explicitly acknowledged by the Guide — unlike the practices the Guide is silent on.
“Development Team”, and 3–9 members
“The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people.”
Terminology and sizing from the 2017 Guide, superseded. The 2020 text says Developers, and gives the typical size for the whole Scrum Team.
Sprint zero
The Scrum Guide does not mention a sprint zero. It says a new Sprint starts immediately after the conclusion of the previous Sprint.
Hardening sprints
“Work cannot be considered part of an Increment unless it meets the Definition of Done.”
The Scrum Guide does not define a hardening or stabilisation Sprint.
The Scrum Master as a manager who assigns work
“They are also self-managing, meaning they internally decide who does what, when, and how.”
The Sprint Review as a release gate
“However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.”
The stand-up rule (Daily Scrum held standing)
The Scrum Guide does not mention standing up. It defines the Daily Scrum by its purpose, participants, timebox, and outcome only.