Operations | Monitoring | ITSM | DevOps | Cloud

Sleuth is pleased to announce a new set of features that enable our customers to measure, compare, and drive efficiency improvements on a per-team basis!

This post is the third in a series of deeper dive articles discussing DORA metrics. In previous articles, we looked at: The third metric we’ll examine, Change Failure Rate, is a lagging indicator that helps teams and organizations understand the quality of software that has been shipped, providing guidance on what the team can do to improve in the future.

This post is the second in a series of deeper dive articles on the four DORA metrics. The first metric we looked at was Deployment Frequency, which is about how often code can get released to end users. In this second article, we’ll look at Change Lead Time, arguably the metric most familiar to developers.

We are excited to announce that Sleuth has raised $22M in Series A funding, led by Felicis, joined by Menlo Ventures with participation from CRV. We’re disrupting the world of engineering efficiency and we're hiring, come join us!

While metrics have always been fundamental to improvement in the business world, the growing prominence of DevOps in recent years has elevated their importance in the context of software development. To build a continuous improvement culture, you need a set of metrics that allows you to establish a baseline and inform where the improvement opportunities lie. Arguably the most popular of them is DORA metrics. In this post, we will focus on Deployment Frequency, one of four DORA metrics.