Measuring Business Value With Metrics

Discussing software development metrics at my place of work, a colleague (Derek Morrison) came up with a neat concept – a way of measuring Business Value.

We’re using Scrum as an agile management framework, estimating in points and measuring Velocity to help plan future Sprints.

For those not familiar with Velocity, it’s the total estimated cost (in effort or points) of the features that are 100% complete (i.e. signed off and delivered) in a Sprint or iteration. If you’re familiar with Earned Value Analysis in more traditional project management methods, it’s basically the same concept.

Each feature, or user story, listed on the Product Backlog has two Fibonacci scores. One for Size and one for Business Value. This is potentially a useful way to prioritise the Product Backlog, as a simple formula (value/size) can be used to order the backlog with the quickest/biggest wins first.

Derek’s idea was to measure the Business Value of what we’re delivering, as well as Velocity for the team’s planning purposes. We referred to this metric as Business Velocity.

We haven’t started using this metric in our teams yet, so it’s too early for me to comment on how it’s working in practice. However I was very interested to see James Shore’s comments on the same.

Personally I think it has merit. So long as – as with all metrics – people don’t play the system.


3 Responses to “Measuring Business Value With Metrics”

  1. bcarlso says:

    We’ve attempted to perform the same thing. I’m afraid it didn’t work out for us that well. The business users didn’t really grasp the concept of relative estimation (8 point story is twice as valuable as a 4 point story and half as valuable as a 16 point story).

    What we ended up with was different areas of the business trying to game the system in order to make their story land as high up the stack as possible.

    We didn’t (and still don’t) have a formal product owner role, so I think that is a large part of it, and we also didn’t ensure that everybody agreed on BV and took an average, which makes the system easier to game. We have since tabled the project and moved on to higher priority projects.

    I’m interested in hearing how well this works for your team.

  2. Kelly Waters says:

    Yes, a single Product Owner for your team – or at least for each product – is an essential ingredient for so many of the benefits of agile development. And certainly for this metric to work.

    In fact, a single, engaged product owner is the key to solving so many development problems, even with a more traditional development approach.


  3. Mecke Blog says:

    Take a look at classic function point analysis ( It actually encapsulates what you are trying to achieve and has a solid economic and statistical basis

Leave a Reply

What is 9 + 1 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”