Hvordan ved vi om vi skaber værdi? De fleste teams er gode til at lave hypoteser, men mindre gode til at bevise dem.
When experimenting with delivering value sooner, a question soon creeps up: ‘How will we know if we deliver value?’ In this article, you will learn why it is important, and that it might not only be relevant for measuring feature value.
The Problem
Most teams I know of today are very good at establishing more hypotheses, but less so at proving the hypothesis. We are often convinced that the features on our product backlog create value in terms of reaching our goals, however we rarely develop the instruments that will allow us to know.
What is a Hypothesis?
A hypothesis is like a scientific hunch—it’s an educated guess or a proposed explanation for a phenomenon. Researchers use hypotheses to guide their experiments and investigations.
Translating this to the features on our product backlog; we identify a user need, a phenomenon, and our educated guess is that the feature will address the need, hoping it will create value for the user. So, the feature implementation works as an experiment to address the user need.
The Real Problem: Rarely do I see companies test if the value is actually realised. This means that we never close the loop to determine if a given feature realises the value we had a hunch it would.
On a practical level, this is the reason we build products with thousands of features, of which only 20% are used. Additionally, as we are not measuring the value of our features, we end up never decommissioning features that are no longer used, making our product unnecessarily complex.
How to Get Started on Measuring Value
- Define the hypothesis for addressing the identified user need in one or more product backlog items.
- Establish a baseline for metrics that will allow you to prove that the feature is providing increased value.
- Build the increment, including the minimum version of the feature (Customer delight should still be in focus).
- Put the feature in the hands of customers and start proving the hypothesis by monitoring the metrics.
- Continuously evaluate if the metrics you have defined are true measures of value. Otherwise, find new and better metrics.
- Keep monitoring the value the feature provides, and if it declines towards zero value for the customers, consider decommissioning the feature, making your product easier to maintain.
Is it easy? Not at all. Does it bring value? It has for me, as it helps focus on the 20% of the features that bring value to customers and helps you deliver value sooner!
It’s Not Only Feature Value
It is not only feature value that is worth measuring – how about agility? “How do we actually know we are agile?” If we do not set up some metrics that make sense for us to determine if we are becoming more agile, then it is hard to say?!
Vil du lære at måle værdi systematisk?
Lad os diskutere hvordan Evidence-Based Management kan hjælpe jeres team med at fokusere på de 20% features der skaber reel værdi.
Book Samtale