📎 Webclip
Is It Time to End the Software Metric Madness?
The page argues that common software delivery metrics, such as deployment velocity, lead time, and bug fixes, show progress in producing software but do not show whether that work creates business value. It uses the example of car manufacturing to show that speed and quality alone are not enough if customers do not buy the product or if it is sold at a loss.
It cites Forrester saying CEOs should end the focus on software metrics alone and instead connect measurement to business outcomes such as profit margin, ROI, and customer acquisition. It presents BizOps as a framework for linking software progress metrics to business success.
Reading notes#
- Deployment velocity, lead time, and bug fixes are described as useful for measuring speed and quality, but not sufficient for judging success.
- The car manufacturer example is used to show that fast production and good quality do not guarantee business success.
- The Pontiac Aztec is mentioned as an example of a product that was produced in volume but did not meet demand or profitability expectations.
- Forrester is quoted as saying CEOs must end the madness of software metrics and replace arcane, indirect measures with business measures.
- The page says organizations should gauge success with business measures such as profit margin, ROI, and customer acquisition.
- BizOps is presented as a framework that connects software delivery measures to business objectives.
