“Software is eating the world.”
— Marc Andreessen
“You can’t manage what you don’t measure.”
— Peter Drucker
ORGANIZATIONS FROM ALL industries are embracing
software as a way of delivering value to their
customers, and we are seeing software drive
innovation and competitiveness from outside of the
traditional tech sector.
For example, banks are no longer known for hiding
gold bars in safes: instead, companies in the financial
industry are harnessing software in a race to capture
market share. Using innovative apps, banks are making it
possible for their customers to do most of their daily
banking in a few swipes, from depositing checks to
transferring money securely between bank accounts.
Moreover, the banks themselves can improve their
service in a number of ways, such as using predictive
analytics to detect fraudulent transactions. Other
industries are seeing similar changes: cars are now
computers on wheels, and even the U.S. Postal Service
is in the middle of a massive DevOps transformation.
Software is everywhere.
Leaders must embrace this new
world or step aside. Gartner Inc. predicts that by 2020, half of the CIOs
who have not transformed their
teams’ capabilities will be displaced
from their organizations’ leadership
teams. And as every good leader
knows, you cannot improve what you
do not measure, so measuring the
software development process and
DevOps transformations is more important than ever.
Delivering value to the business
through software requires processes
and coordination that often span multiple teams across complex systems,
and involves developing and delivering software with both quality and resiliency. As practitioners and professionals, we know that software
development and delivery is an increasingly difficult art and practice,
and that managing and improving any
process or system requires insights
into that system. Therefore, measurement is paramount to creating an effective software value stream. Yet accurate measurement is no easy feat.
Measuring DevOps. Collecting
measurements that can provide insights across the software delivery
pipeline is difficult. Data must be complete, comprehensive, and correct so
that teams can correlate data to drive
business decisions. For many organizations, adoption of the latest best-of-breed agile and DevOps tools has
made the task even more difficult because of the proliferation of multiple
systems of recordkeeping within the
One of the leading sources of cross-organization software delivery data is
the annual State of DevOps Report
(found at https://devops-research.
2 This industry-wide survey provides evidence that
software delivery plays an important
role in high-performing technology-driven organizations. The report outlines key capabilities in technology,
process, and cultural areas that contribute to software-delivery performance and how this, in turn, contrib-
Article development led by
Your biggest mistake might
be collecting the wrong data.
BY NICOLE FORSGREN AND MIK KERSTEN