What does it mean that “Scrum is a … framework…” (from the Scrum Guide).
Let’s give this a closer look.
From Cambridge Dictionary:
Framework:
- “A supporting structure around which something can be built”
- “A system of rules, ideas, or beliefs that is used to plan or decide something”
As a framework, Scrum provides us a rack to hook up practices, techniques, methods, etc. Yet also lets us easily replace these with better ones as we discover them. A framework does not provide you with these specific practices; it lets you choose what works in your context. The framework does not force you to use story points, velocity, burn charts, user stories, Jira, or whatever practices and tools you are currently using. These should be what works for your team in their context.
The definition of “framework” also says that it is about building something. What can Scrum build? Scrum on itself… Nothing. Building is in the hands of the teams. Yet, Scrum brings us a focus working towards goals, and supports us planning towards these. It helps us build teams that become more and more effective in delivering value for the product’s users.
Therefor teams can use Scrum to build (almost?) any complex product or service.
So, what for are you using Scrum as a framework? What are you building? How does Scrum support you? How does it allow you to replace practices and techniques by better ones?
I hope you find value in these short articles and if you are looking for more clarifications, feel free to take 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!
