Defining value in Scrum: how do you know if you're truly adding value?

What does value mean in Agile and Scrum?

In Agile and Scrum, value refers to the impact a product or feature has on the end-user, the business, or other stakeholders. It's not just about 'delivering something,' but about the effect your work has. Whether you're adding a new feature or improving an existing process, value is about the extent to which you contribute to your organization's goals and the benefit for your customers.

‍

How do you define and measure value?

Value differs by context: an e-commerce site might measure revenue, while a government agency considers customer satisfaction more important. To identify value, it's smart to use 'value metrics':

• Financial metrics: ROI, revenue growth, cost savings.
• Customer satisfaction: NPS score, customer reviews.
• Usage and adoption: number of active users, frequency of use.
• Operational efficiency: reduced lead time, fewer errors or customer inquiries.

‍

Value versus output (difference between 'value' and 'work')

'Doing more work' doesn't necessarily mean 'delivering more value'. Output can be high without serving the customer's goals. In Scrum, you prefer to focus on small increments with demonstrable value, instead of an avalanche of features that might not be used.

‍

Techniques for value assessment (ROI, customer satisfaction, etc.)

• Return on Investment (ROI): ideal for determining if a feature is financially viable.
• Customer Satisfaction: measure feedback through surveys, NPS, or user tests.
• Opportunity Scoring (Kano Model): identify which features are essential, which create a 'wow' effect, and which are superfluous.
• User Engagement: track metrics such as average session duration or repeat visits.

‍

Examples of Clear and Vague Value Definitions

• Clear: “With this feature, we expect 20% more new customers within 3 months.”
• Vague: “We want the user interface to look nicer.”

‍

Practical Methods to Make Value Measurable

• Link each user story to a specific goal or metric. This way, the team knows exactly what they are working on and why.
• Have the Product Owner evaluate each sprint to see if the added increment has actually delivered results.
• During the Sprint Review, discuss not only what has been built, but also what value the increment delivers or can deliver.

‍

How do you prevent only measuring output?

• Focus on the end-user or customer: ask if what you've built truly helps them.
• Set SMART goals for the items in your Product Backlog.
• Use experiments (A/B tests, pilots) to see if your ideas truly have an impact.

‍

Conclusion

Defining value in Scrum means looking beyond 'more features' or 'more output'. You focus on tangible impact and constantly check if it's truly being achieved. Through clear metrics, customer feedback, and a culture of experimentation, you ensure that every increment truly contributes to your organization's goals and user satisfaction.

‍