Project delivery
Scrum
Thirteen pages, and most of what people call Scrum is not in them
What the Guide actually says: one team with three accountabilities, five events inside a container, three artifacts with three commitments — and the long list of familiar practices it never mentions.
Start the map 5 pillars · 15 cards · about 22 minutes end to end
The map
Five minutes, once. Rate each pillar before you start and the cards you are shakiest on come first. Skipping it costs you nothing but the ordering.
-
Theory — what Scrum is
A framework founded on empiricism, deliberately incomplete, and immutable in its parts.
-
The Scrum Team
One team, three accountabilities, no sub-teams and no hierarchy.
-
The five events
The Sprint is a container; the other four exist to inspect and adapt inside it.
-
Three artifacts, three commitments
Each artifact carries a commitment, and the commitment is what makes it transparent.
-
What the Guide does not say
Ceremonies, grooming, story points, velocity — none of them appear. This is where most teams drift.
Apply it
One scenario per sitting, about ten minutes. No marking scheme that pretends to be objective — a rubric you are invited to argue with.
Read against The Scrum Guide, November 2020 (Schwaber & Sutherland) on . Regulations and frameworks change; the date is there so you can tell whether this has kept up.
The Scrum Guide is published by Ken Schwaber and Jeff Sutherland under CC BY-SA 4.0. These cards are independent commentary written in our own words, not a derivative of the Guide's text. ytyk.org is not affiliated with, endorsed by or licensed by Scrum.org, Scrum Alliance or the Guide's authors.