Skip to main content
Enterprise Agile Planning Image

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Dec 12, 2008 — Enterprise Agile Planning expert

Precision of Measurement Is No Guarantee of Usefulness of What’s Measured

Enterprise Agile Planning

One of the main myths of traditional project management relates to measurement precision. Traditional project managers have numerous statistical tools in their arsenal. Such measures as earned value or cost performance indicators etc. are touted as providing a precise scientific measure of how we’re doing. All of this points back to a Tayloristic view of software and product development. To put it another way we assume that developing software is a clearly defined process and thus amenable to scientific measurement and monitoring.

The problem is, as most proponents of agile development methods know, product development isn’t, for the most part, a defined process amenable to statistical process control. That’s one of the reason empirical methods like Scrum were developed. Given that, the value of these measurements no longer depends on their precision, if it ever did. And yet we often continue to try and apply these kinds of measurement to our process and its output, often at considerable cost.

Early in the 19th century, reputable scientists performed many precise measurements using an assortment of mechanical calipers on human heads. Using a complex and detailed map of the 27 brain “organs” reflected in the various bumps and fissures on the skull could determine such aspects of the individual’s personality as “comparative sagacity,” “cleverness,” or “poetical talent.”

“In its heyday during the 1820s-1840s, phrenology was often used to predict a child’s future life, to assess prospective marriage partners and to provide background checks for job applicants.” (

Likewise, attempts at precise and detailed statistical process control of what is an inherently imprecise and empirical process like software development also offers little or no predictive power and amounts to unnecessary overhead with little or no business value. The results from the extremely simple means we use in Scrum to track progress and plan releases (e.g. burndown charts, velocity tracking etc.) provide more value for less effort. Our measures are intentionally imprecise to reflect the uncertainty of what we do. And yet as part of an empirical process model with short inspect-and-adapt feedback loops we know as much, or more, about our efforts than someone taking detailed and precise measurements while simultaneously not giving the false impression that we know more than we do.

Jimi Fosdick

Download the PDF version: Precision of Measurement_blog

More from the Blog

View more
Jul 27, 2021 Becomes First to Achieve FedRAMP Moderate “In Process” Status for Enterprise Agile Planning Solution

Enterprise Agile Planning, the leading AI-driven DevOps value stream delivery, and ma ...
Read More
Jun 21, 2021

How Agile can be implemented effectively across the organization

Enterprise Agile Planning
Just a few decades ago, a “disruption” was seen as an undesirable thin ...
Read More
May 31, 2021

Agile change management processes are key to delivering software faster

Enterprise Agile Planning
With its emphasis on delivery value faster, agile product management s ...
Read More
May 03, 2021

Bringing the agile planning approach to your whole business

Enterprise Agile Planning
The events of the last 12 months have demonstrated that the only sure ...
Read More
Contact Us