Skip to main content

Measuring Value

Last post 11:17 am March 11, 2016 by Ian Mitchell
1 reply
03:38 am March 11, 2016

What do you think about this article's assertion that many scrum teams focus on delivery metrics rather than value metrics?

http://blog.invisionapp.com/track-designs-effectiveness/

What value metrics do you use to measure product effectiveness after a sprint has shipped?


11:17 am March 11, 2016

Drawing a distinction between delivery metrics and value metrics may not be helpful, given that Scrum actually focuses on delivering value.

What matters is being able to close the validated learning loop by releasing that value under market conditions. There aren't really any good or bad metrics per se. Rather, the measures we use can be either "actionable metrics" (good) or "vanity metrics" (bad) depending on context. As the article says, a success factor or hypothesis should be decided at the start of an initiative. That frames the context. Metrics should test the hypothesis as rigorously as possible so the smartest actions can be taken.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.