# How to measure value? Part 4

Published on SogetiLabs, date April 28th, 2016: http://labs.sogeti.com/how-to-measure-value-part-4/

Relative weighting

In Part 1Part 2 and Part 3,  I explained Theme Screening and Theme Scoring. In Theme Screening we added a weight and made the scoring more relative.

Relative weighting takes the weight factor of Theme Screening to another level and adds the teams estimate to the equation to make a new ranking within the Product Backlog.

Consider the Backlog we have been working with so far:

 1 Cinnamon Apple Cupcake 2 Liquorice Mint Cupcake 3 Green Tea, Honey Cupcake 4 Pecan Salty Caramel Cupcake 5 Lemon White Chocolate Cupcake

In Relative Weighting we look at the following per theme:

• What is the impact of implementing this theme scored from 1 to 9.
• What is the impact of not implementing this theme scored from 1 to 9

We add these two values together per theme and this is the “Value” of the theme.

Then we determine the relative estimation per theme. This is the “cost” of the theme.

Both these need to be normalised to make it usable in the future. After all, a backlog is not a fixed list. We can do this by making the “Value” and “Cost” variables into percentages. Add up all the values and all the costs and determine per value-variable and cost-variable what this represents as a percentage of the whole.

Then we divide the Value percentage by the Cost percentage. This represents a very pure ROI number of the theme. This ROI number we can use to rank the Theme in the full list.

What I like about this way of determining value is that it actually relates it with the costs as well. Mind you, this does mean that you have to have sessions with your development team to discuss the Theme before you can rank it in your list. To be honest, I expect the Product Owner to involve the team anyway in the Backlog Refinement sessions every week.

Let’s look at the Matrix again:

 Cupcake => Theme V Benefit Penalty Value (benefit + penalty) Value % Estimation (totals of PBI’s) Estimation % ROI (Value% /Est.%) Liquorice Mint 3 2 5 8.33 54 27.69 0.30 Green Tea, Honey 8 4 12 20.00 43 22.05 0.91 Cinnamon Apple 9 8 17 28.33 35 17.94 1.58 Pecan Salty Caramel 8 8 16 26.67 25 12.82 2.08 Lemon White Chocolate 5 5 10 16.67 38 19.48 0.86 Totals 60 100 195 100

Considering the highest ROI gives the following ranking:

 Rank Theme Relative Weight 1 Pecan Salty Caramel Cupcake 2.08 2 Cinnamon Apple Cupcake 1.58 3 Green Tea, Honey Cupcake 0.91 4 Lemon White Chocolate Cupcake 0.86 5 Liquorice Mint Cupcake 0.30

Looking back at the different methods to calculate value I have a slight preference for Relative Weighting when I consider the full ROI focus I expect a Product Owner to have. It is still a tool and Agile considers tools to be important only if they support interaction.

What tool you choose is up to you as “value optimizer”. Make sure that it matches your environment and product.

You could also use more than one tool. I can imagine that the first setup of a Product Backlog when you have not selected a development team yet is best helped by Theme Screening or Scoring. Without the estimations of the team the ROI calculated in Relative Weighting is too unsure. At least determine with your stakeholders what is important to get ready for the new team first. But involve existing or new to form development teams in your determination of Product Backlog items.

For this technique there is also a tool on Mike Cohn’s site

In the past 4 blogs I have given you some tools. I would like to remind you of the first value of Agile:

We value: Individuals and interactions over processes and tools
agilemanifesto.org

The use of tools should not interfere with your work as Product Owner with your team(s).

You as Product Owner are accountable for Return of Investment, most of the time with the research that you do and the stakeholders you work with you get a feeling of what is value for you and your product. With the tools I have given you it is easier to quantify this feeling. Don’t ignore your feelings though. The best result from Agile product development comes from focussing on the outcome as opposed to the output. Outcome is usually user satisfaction not short term profit.