You can improve the effectiveness of your development teams by applying the right DevOps measurement strategy.
Software development teams have been measured in ways that don’t always make sense.
A good example of this was when dev teams were measured by the number of lines in the code they wrote, or Ops teams were measured by the number of tickets they resolved.
What was the main problem with this kind of metric? Organizations were not really measuring the productivity and capabilities of their teams nor considering the complexities of the work. They also did not consider their teams as a whole. They looked at metrics from individual team members, rather than evaluating the effectiveness of the team.
So, knowing this, how should I measure the performance of my teams?
About the Author
|Matias Caniglia, Director of DevOps and Platform Engineering at Forte Group. With over 15 years of experience in the IT industry, Matias is a passionate and skilled DevOps Architect who delivers cloud-based solutions, monitoring, and continuous integration and delivery for various projects and clients.|
In 2014 Nicole Forsgren, Gene Jim, and Jez Humble started the DORA (DevOps Research and Assessment) reports, which focus on the study and promotion of DevOps practices. They conducted comprehensive research on the practices and metrics that drive exceptional performance in software development and delivery.
Thanks to the work that the DORA team has done during the last decade, we now know that there are more efficient ways to measure the performance of our teams using metrics like the lead time for changes, the deployment frequency, the change failure rate, and the time to restore services. Organization are now dealing with how to measure these metrics and how to properly implement them.