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.
The larger your team grows and the faster your teams move, the harder it is for engineering leaders to find trust but verify moments, the moments where you should dig in and make sure your team's health is improving. Imagine a world where all your engineering tools are working together such that accurate and insightful trust but verify moments come to you. Imagine a world where you have the finest Sleuth in the world, working just for you.
DORA metrics come from an organization called DevOps Research and Assessment. This was a team put together by Google to survey thousands of development teams across multiple industries, to try to understand what makes a high performing team different than a low performing team. What they ended up settling on are these four metrics.
In Sleuth’s continuing efforts to help our customers to deliver faster and safer, we have always put security as a top-level business priority. Security and privacy of our customers’ data is always in the forefront of our design, development, and deployment concerns. We understand the level of trust our customers put in us when they connect key systems together with Sleuth.
Today we’re excited to be rolling out a completely redesigned Sleuth experience. Our new Command Center provides one place to visit so developers can quickly and safely deploy new changes.
Data from monitoring tools like Datadog are useful for developers to help them understand whether the code they've deployed is healthy or needs to be fixed or rolled back, or when there is an incident to investigate. As a deployment mission control, Sleuth helps developers see metrics data from a developer-centric point of view - by deployment - and interpret such data for them.
One of our most commonly requested integrations, Datadog cloud monitoring, was announced last week on the Datadog blog! Sleuth organizes your deployments into projects, which collect and organize key data from your code sources and their associated staging environments. This data consists of metrics and errors.
At times, directing projects in multiple locales from a desktop or laptop feels like conducting an orchestra in the dark. Coordinating with diverse, remote teams of developers producing software on an agile schedule of continual updates and releases can be especially nerve-wracking. At Sleuth, we’re crushing the remote-work challenge because, in 20 years of managing from afar, we’ve learned a thing or two — actually three — about how to do it right.
