Filter by Tag

Michael Gaskin from Puma describes how his team uses Sleuth to orchestrate its entire deployment pipeline and show software engineering value.

With Sleuth's latest release, work-in-progress dashboards provide real-time visibility into work that hasn't yet deployed, and highlight risks to address before they affect efficiency.

How do you continually improve on DORA metrics? Learn four tips to get to the next level of your DORA metrics journey.

Sleuth is pleased to announce a new option to start your Change Lead Time clock based on state transitions in your issue tracker!

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 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.

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.

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.

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 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.

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.

New team-centric views allow you to measure, compare, and improve DORA metrics over time on a per-team basis.

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 insights create opportunities for teams to improve and speed up their processes, ensuring users get access to features faster.

Read about our journey to make engineering efficiency easy to measure, accurate, and easy to improve.

What is Deployment Frequency and how does measuring it aid continuous improvement in software development? Learn about it here.

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.

Comparison guide of engineering productivity tools for measuring DORA metrics / Accelerate metrics, including Sleuth, LinearB, Haystack, Faros, Code Climate Velocity

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.

Sleuth metrics tracker is he most accurate and flexible way to track and improve your team's Accelerate (DORA) metrics.

MTTR is defined by DORA and in the Accelerate book as '"how quickly a service can be restored after a failure".

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".

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.

Don Brown explains what the four DORA / Accelerate metrics are, and shares practical recommendations on how to improve each one.

Sleuth has continued to pursue key independent third-party validations of our security, processes, and services.

What's new at Sleuth: Command Center, redesigned code deployment dashboard and deploy details view, deploy locking, and environment drift tracking.

With Datadog integration, Sleuth gives developers visibility into all metrics tracked in Datadog from a deployment point of view.

Developer teams shipping software frequently are in a constant state of change.

Nowadays, software development teams utilize continuous delivery or some variation, to create better, faster, more accurate software releases.

Being in the DevOps space, we're often asked questions about software deployment like, "What's the difference between continuous deployment and continuous delivery?"

Quick, do you know what code is currently deployed to production? How about staging? How far apart are these environments? Sleuth tracks ...

In order to have the most successful deployment, there are a few best practices that software development teams should be mindful of. Fir...

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.

Deploying a new feature to production is a momentous occasion.

With the introduction of impact tracking Sleuth, know your impact in realtime!

Building a healthy productive engineering culture is hard and just deploying frequently with continuous deployment is not enough.

If you are hearing all these wonderful things about Continuous Deployment (CD), and think, "There must be a catch," well, you are right.

With Sleuth's new Impact modeling, you can now assess the impact of a deployment whether using an error tracker or not.

At the April Test In Production Twitch presentation, Sleuth CEO Dylan Etkin and Yoz Grahame, LaunchDarkly developer advocate, laid out st...

When your boss asks you what you did this week, how do you answer her?

The software delivery team is a critical component of the DevOps of any organization.

At Sleuth, we are committed to bringing order to DevOps.

Find out how Sleuth's automatic deployment locking can help prevent code catastrophe.

Today, we’re excited to announce you can now integrate LaunchDarkly with Sleuth.

One of the best things about tracking deploys is knowing what and when code is shipped.

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.

Tracking deploys means knowing what and when code is shipped. Let Sleuth generate your release notes and post them to Slack.