The truth is that measuring things in software development is hard. As Edwards Deming clearly stated “The most important things cannot be measured.” We’ve all seen how metrics can be gamed and abused (velocity, anyone?) and many have heard of the “Law of Unintended Consequences” and experienced in practice how measurement led to unintended and counterproductive behaviors. So a lot of folks have jumped on the #NoEstimates bandwagon and we’re all better off not measuring anything at all, right?
I’m not sure it’s that easy. The reality is that we’re all living in the business world and we’re being asked to help answer certain, very valid questions, such as:
- What’s our customer satisfaction? How is it trending?
- How are our Agile teams doing? Are we getting better?
- How is our Agile / digital transformation progressing?
- Are we getting the value we were hoping for out of our transformation efforts, coaching, etc.?
- What ROI are we getting from the money we invest in our transformation?
- For consultants and coaches: Am I moving the needle and making an impact?
- Are we helping the organization deliver value faster?
- Where do we need to deploy our limited coaching resources?
- What bottlenecks in our value streams do we need to address?
While measurements are hard and there are certainly landmines to avoid, … Continue reading my full post here.