Computer Desk and Monitor

How do you reduce incident resolution time? (MTTR)

A while back I spoke about what is MTTR and MTTD and why they matter in software delivery or at an organization. Today I’ll go in a bit more in depth and talk about how to reduce incident resolution time at your company. First, I’ll go into some general basics but this article assumes you already understand MTTR and are able to measure it. If you aren’t there yet, I can write another article or read my previous one to get an idea. Let’s get into it! How do you reduce MTTR? (mean time to resolution) Mean Time to Resolution

Change failure rate

What is change failure rate and what to look for?

For today’s article I’ll talk a little about change failure rate and what it might mean to your organization. I cover it ever so briefly in the DORA metrics article I posted a while back. I’ll go a bit more in depth here today. What is change failure rate? Change failure rate is a metric used in the software delivery process to quantify the percentage of times a change, such as a new feature, bug fix, or configuration update, results in a negative outcome, such as a degraded user experience, system outage, or rollback. This metric helps organizations understand the

DORA Metrics: Software Delivery Performance & Adoption Challenges

Hello all! Here with another article. One of my favourite implementations that I’ve done in my agile software delivery consulting days and where I saw a large driver of culture change. That’s DORA Metrics. I’ve also recently spoken about WIP limits and their general importance so be sure to check that out as well. Off we go. What are DORA metrics? The DevOps Research and Assessment (DORA) metrics are a set of key performance indicators (KPIs) designed to measure the effectiveness of software delivery and operational performance. Developed by experts in the field of DevOps, DORA metrics help organizations evaluate