Scrum doesn’t tell people what to do.
It offers a few clear, simple rules—and trusts teams to play the game wisely.
As the Scrum Guide says:
“Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.”
According to the Cambridge Dictionary, a rule is:
“An accepted principle or instruction that states the way things are or should be done, and tells you what you are allowed or not allowed to do.”
Think of it like Stratego. Or chess. Or any game you love:
- The rules don’t guarantee a win.
- The rules don’t tell you how to play.
- But they create shared boundaries that make the game possible, fair, and meaningful.
The same goes for Scrum.
Just like chess doesn’t tell you how to win, Scrum doesn’t tell you how to build your product.
In fact, the Scrum Guide even calls itself:
“The Definitive Guide to Scrum: The Rules of the Game.”
Looking at the Scrum Guide we see several sections:
Not rules, but essential:
- Scrum Definition – what Scrum is (and isn’t)
- Scrum Theory – empiricism and lean thinking; the foundation to play well
- Scrum Values – how we behave to be more successful using Scrum
Then come the actual rules:
- Scrum Team – three accountabilities. Defined, non-overlapping. All required to play Scrum.
- Scrum Events – five events, no more, no less. Each with a clear purpose and deep links to Scrum theory.
- Scrum Artifacts – three artifacts, each with a commitment. Again grounded in Scrum’s theory.
Not rules, but an important reminder:
- End Note – if you want to play and call it Scrum, follow the rules. Just like chess stops being chess if you ignore its rules. And that’s OK. Your call. Just don’t blame the game if there’s no flow—or no fun.
Scrum doesn’t define tools, templates, refinement steps, or what metrics to track. That’s the team’s job.
The rules define what must exist, not how to execute.
Like any good game, Scrum has very few rules—on purpose:
- So teams can solve complex problems
- So they can self-organize and adapt
- So they’re not boxed in by heavy process
Scrum’s rules are the minimum boundaries. Everything else is strategy—not law.
Time to reflect:
When was the last time your team reviewed the rules it's following?
Are you playing the full game—or have you unknowingly rewritten it?
I’d love to hear your thoughts in the comments below!
I hope you find value in these short articles and if you are looking for more clarifications, feel free to make contact.
Don't want to miss any of these blog posts? Have the “The Scrum Guide Explored” series weekly in your mailbox.
Wishing you an inspiring read and a wonderful journey.
Scrum on!
