Announcing Work-in-Progress Metrics for Sleuth
With Sleuth's latest release, customers get work-in-progress dashboards that provide real-time visibility into work that hasn't yet deployed, and highlight risks to address immediately before they affect efficiency.
Level up your DORA metrics journey
How do you continually improve on DORA metrics? Learn four tips to get to the next level of your DORA metrics journey.
Announcing issue-initiated Change Lead Time
Sleuth is pleased to announce a new option to start your Change Lead Time clock based on state transitions in your issue tracker!
Does accuracy matter for tracking DORA metrics?
You can take DORA metrics at face value, but you won't get many insights. Read how accurate DORA metrics help you ask better questions to get better answers.
Can, how and should you measure developer productivity?
Can developer productivity be measured? And if so, how do you measure it? But first, should you even measure developer productivity? And is developer productivity related to DORA metrics? Get key insights here.
How to learn from software failure
Two of the four DORA metrics, Change Failure Rate and MTTR, require that you define what failure means. How exactly do you do that? And how can you learn from software failure when it happens? Get some insight right here.
How to use DORA metrics
You buy into DORA metrics. Now what? How do you use DORA metrics to improve your team's software delivery performance? We offer four tips.
The DORA metrics backstory
We talk a lot about what DORA metrics are and how to measure them. Let's take a step back and learn their history and why we use them.
Cycle Time explained
Cycle Time isn't a DORA metric, so how did it make it into this series? Because Cycle Time is another metric that can empower your team to improve productivity.
Mean Time to Recovery (MTTR) explained
A strong Mean Time to Recovery (MTTR) increases trust among end users. Learn the causes and impacts of poor MTTR (a DORA metric) and how to improve it.
Announcing DORA metrics for teams
New team-centric views allow you to measure, compare, and improve DORA metrics over time on a per-team basis.
Change Failure Rate explained
Like all DORA metrics, Change Failure Rate is a measure of maturity and quality for teams and organizations. Learn all about it here.
Change Lead Time explained
Change Lead Time insights create opportunities for teams to improve and speed up their processes, ensuring users get access to features faster.
Sleuth raised $22M Series A to help teams track and improve engineering efficiency
Read about our journey to make engineering efficiency easy to measure, accurate, and easy to improve.
Deployment Frequency explained
What is Deployment Frequency and how does measuring it aid continuous improvement in software development? Learn about it here.
How to define software failure
Two of the four DORA metrics, Change Failure Rate and MTTR, require that you first define what failure means. Does failure always mean incident? Or should failure mean rollback? Here’s how to define failure, and how Sleuth does it today.
DORA metrics: Best trackers comparison guide [Sep 2021]
Comparison guide of engineering productivity tools for measuring DORA metrics / Accelerate metrics, including Sleuth, LinearB, Haystack, Faros, Code Climate Velocity
Why devs need to be involved in production - a story from the trenches at Atlassian
A story from Don's time at Atlassian back when they tended to release software every 2-3 months, and why developers need to be involved in deploying to production.
Stories from the Trenches
"Accelerate" your team with Sleuth
Sleuth metrics tracker is he most accurate and flexible way to track and improve your team's Accelerate (DORA) metrics.
What is Mean Time to Recovery (MTTR)?
MTTR is defined by DORA and in the Accelerate book as '"how quickly a service can be restored after a failure".
What is Change Lead Time?
Change Lead Time is defined by DORA and in the Accelerate book as '"the time it takes to go from code committed to code successfully running in production".
What is Deployment Frequency?
Deployment Frequency is defined by DORA and in the Accelerate book as '"a software deployment to production or an app store", and is used as a proxy for batch size.
DORA metrics explained
Don Brown explains what the four DORA / Accelerate metrics are, and shares practical recommendations on how to improve each one.
Sleuth + SOC 2 Type II: Our constant commitment to security
Sleuth has continued to pursue key independent third-party validations of our security, processes, and services.
Developers, take command of your deploys
What's new at Sleuth: Command Center, redesigned code deployment dashboard and deploy details view, deploy locking, and environment drift tracking.
Track Datadog metrics in Sleuth
With Datadog integration, Sleuth gives developers visibility into all metrics tracked in Datadog from a deployment point of view.
Track, Debug, and Fix Errors with Sleuth and Sentry
Developer teams shipping software frequently are in a constant state of change.
Set Up Your Deployment Pipeline Like a Rockstar!
Nowadays, software development teams utilize continuous delivery or some variation, to create better, faster, more accurate software releases.
Continuous Deployment vs. Continuous Delivery: What is the difference?
Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?"
Track deploys by environment with Sleuth's first-class environment support!
Quick, do you know what code is currently deployed to production? How about staging? How far apart are these environments? Sleuth tracks ...
Deployment Tracking Is Critical for Software Teams. Here's Why.
In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. Fir...
The 2020 SaaS Startup <$100 Essential Toolkit
I’ve recently co-founded a startup, and after working so long in more mature enterprises with diverse toolchains, it was actually massively educational to return to first steps and figure out what our critical needs were, balanced with essentially zero budget.
Mitigate risk with rolling deployments
Deploying a new feature to production is a momentous occasion.
Real-time deployment impact tracking and notifications
With the introduction of impact tracking Sleuth, know your impact in realtime!
Craft Team Culture by Celebrating Deployments
Building a healthy productive engineering culture is hard and just deploying frequently with continuous deployment is not enough.
Three Continuous Deployment mistakes and how to avoid them
If you are hearing all these wonderful things about Continuous Deployment (CD), and think, "There must be a catch," well, you are right.
Impact for Everyone!
With Sleuth's new Impact modeling, you can now assess the impact of a deployment whether using an error tracker or not.
Impact in Production - Sleuth and LaunchDarkly
At the April Test In Production Twitch presentation, Sleuth CEO Dylan Etkin and Yoz Grahame, LaunchDarkly developer advocate, laid out st...
I deploy, therefore I am
When your boss asks you what you did this week, how do you answer her?
The 10 DevOps Best Practices Every Software Team Should Adopt
The software delivery team is a critical component of the DevOps of any organization.
Sleuth Accelerated - Announcing Our Seed Round!
At Sleuth, we are committed to bringing order to DevOps.
Prevent unwanted changes with Sleuth deployment locking
Find out how Sleuth's automatic deployment locking can help prevent code catastrophe.
Integrating LaunchDarkly with Sleuth
Today, we’re excited to announce you can now integrate LaunchDarkly with Sleuth.
Track What You're About To Deploy
One of the best things about tracking deploys is knowing what and when code is shipped.
Does Your Team Know What Your Code Is Doing Right Now?
Software development teams do more than write and deploy code. Sleuth provides constant clarity on what your deployment tools are doing (or not) to satisfy each team member's needs.