From the Scrum Guide: “The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.”
In a previous musing, I discussed the Increment from the perspective that it is additive—it builds on all prior Increments, and everything keeps working together seamlessly.
This time, I want to draw your attention to the adjective “valuable.”
What Does a “Valuable Increment” Mean?
The Cambridge Dictionary defines ‘value’ as “the importance or worth of something for someone.”
Value is a powerful concept because it isn’t one-size-fits-all. Value is subjective—tied to context and unique to each person, team, or organization. In Scrum, the Increment must deliver value to someone—typically your users, whether they’re internal or external.
Thinking about for whom we are building solutions or solving challenges, it’s for our users. The Increment should be valuable to them.
What does “value” mean to your users? Do you know? Have you checked with them?
Value could mean:
- Reducing effort
- Raising quality
- Reducing risk
- Learning something new
- ...
The key is: don’t assume. Go talk to your real end users. Only then can you truly understand what they are looking for and if what they receive is the value they expect.
When speaking with users, they might ask for specific features or solutions. But remember: features are not value—they are a means to value.
Ask deeper questions:
- Why do they want this feature?
- What problem will it solve for them?
- How will it help them achieve their goals or improve their lives?
By understanding the why behind their requests, you can focus on delivering meaningful value instead of simply fulfilling a checklist of features.
When do users perceive, feel, or receive value?
The answer is simple: when they can use your solution—your Increment.
Until your product is in the hands of users, its value to them is zero, no matter how much effort you’ve put into it. Not released = zero value.
In Summary:
Value in Scrum is:
- Subjective and contextual
- Achieved through delivery
- More than features: It’s about making users’ lives better
To ensure your Increment is valuable:
- Engage with users to understand their needs.
- Dig deeper into their requests to uncover the real problems and goals.
- Release frequently so they can experience the value.
How does your Scrum Team ensure each Increment is adding value for your users? How is it moving you forward toward the Product Goal?
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 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!
