“The Easier It Is To Quantify, The Less It’s Worth”

This content is syndicated from Jim Highsmith by Jim Highsmith. To view the original post in full, click here.

This quote from Seth Godin (Linchpin, 2010), sparked my thinking about metrics and outcomes. It parallels what I’ve quipped in presentations, “I’d rather have a fuzzy measure of something important than a precise measure of something unimportant.” In Measuring and Managing Performance in Organizations (1996) Rob Austin discusses the difference between desired outcomes and performance measures—and that those are likely to be in conflict with one another. Because of the difficulties in finding good measures for desired outcomes, we often substitute things that are easy to measure, but that cause long-term damage. Assessing the desired outcome of programmer productivity by measuring lines of code is a classic misuse of a metric. Historically we assess project success, or failure, by measuring scope, schedule, and cost—especially cost and schedule because they are easy to measure (think earned value analysis). However, the desired outcome, from a customer perspective is to receive a releasable product, of acceptable quality, within a set of constraints (schedule or cost for example). For most projects, rather than asking, “Did we implement all the requirements (a scope question)?” the question should be “Can we release this product now?” Accessing release-ability (a value-oriented question) and quality may be “fuzzier” than measuring cost and schedule, but just maybe they are closer to representing the customer’s true desired outcome.

One Response to ““The Easier It Is To Quantify, The Less It’s Worth””

  1. Ahmed says:

    I don’t think there is a relation btw easy to quantify and less value, ‘cos it could be easy to quantify and more value e.g. customer satisfaction, within 10 seconds you will know whether he likes your product or not.
    Also, I don’t know where is the relation btw releasability and value. I can release a product 50 times per day with no value to customer, only fixing irrelivant issues and features.
    Thanks,
    Ahmed.

Leave a Reply

What is 4 + 9 ?
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 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.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA