The Scrum Guide states that Scrum “only defines the parts required to implement Scrum theory.”
From Cambridge Dictionary:
“Required: necessary according to the rules or for a particular purpose.”
In a Professional Scrum context, that particular purpose is clear:
To implement Scrum theory—empiricism and lean thinking (see Scrum Feels Broken? Maybe You Missed the Theory...).
“Required” doesn’t mean “best practice,” “good to have,” or “standard operating procedure.”
It means: you need it to make the theory work, so Scrum can truly help people, teams, and organizations (see Is Scrum Helping You? Discover How to Uncover Its Real Value.
No more. No less.
Scrum doesn’t define what’s convenient, familiar, or traditional. It defines only what’s essential to generate value (see Defining Value in Scrum: What Does It Mean for You?).
To implement Scrum theory, you need:
- Scrum Values → to guide behavior and foster trust
- A cross-functional, self-managing team with clear accountabilities → so decisions around what, who, when, and how are made close to the work
- Timeboxed events → to enable focused inspection and real-time adaptation
- Minimal artifacts with clear commitments → to ensure transparency and guide evidence-based decisions
Everything else—processes, tools, templates, techniques—is left out on purpose.
Why? Because your context completes the framework.
Many teams “extend” Scrum before they’ve fully implemented the required parts. For example:
- Adding reporting dashboards before creating usable Increments or a transparent Product Backlog
- Chasing velocity charts before establishing a meaningful Product Goal or Sprint Backlog
- Adopting estimation frameworks before creating shared understanding or a solid Definition of Done
If Scrum isn’t delivering results, it’s rarely because something’s missing.
It’s usually because something fundamental (which doesn’t mean easy) isn’t being used effectively.
Let’s remind ourselves:
- Scrum is incomplete by design, so you can experiment
- But it is complete enough to get started
- Try it as-is, use it to learn, and then evolve it deliberately (see Scrum Not Working? Try It As Is Before You Modify It)
Any tool, technique, or extension should reinforce Scrum theory—not distract from it. Not for theory’s sake, but to help your team deliver more value.
Time to reflect:
- Are you applying all the parts Scrum defines to support empiricism?
- Have you added practices that dilute transparency, inspection, or adaptation?
- What would change if you focused more on what’s required—not just what’s familiar?
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!
