Are you feeling more confident that measurement and Agile can coexist? We certainly hope so! As you may have seen in the previous posts (1, 2, 3) of this blog series, many Agilists may shy away from measurements and metrics, but there are ways to not only make it safe for organizations to measure, but even derive great value from the insights gained.

Welcome back! As we’ve seen in parts one and two of this blog series, many Agilists may shy away from measurements and metrics, but we discussed ways to not only make it safe for organizations to measure but even derive great value from the insights gained.

In this blog series, we’re continuing to explore measurement and metrics in the Agile space to help organizations and teams be more successful. If you missed part one, you can read it here.

In this four-part blog series, we’ll explore measurement and metrics in the Agile space to help organizations and teams be more successful.

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?