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

Cycle time formula

Cycle time formula in software delivery

It’s been a bit busy but I’m back with a requested article. How to calculate cycle time via a formula. This will be a quick article as calculating cycle time is really quick. For more in depth information, make sure you check out my article on DORA metrics and WIP limits. With that said, let’s define cycle time and go from there. What is cycle time? Cycle time in software delivery is a key metric used to measure the efficiency and effectiveness of a development process. It’s the amount of time from when work begins on a piece of software

Software delivery team on board

Why does MTTD & MTTR matter for software delivery?

I’m back with another article! This time i’ll talk a bit about MTTD and MTTR and why they matter and how they relate to each other. You can review some of my articles on DORA metrics, change failure rate and more on my website. First we’ll start off with MTTR and why it’s important. What is MTTR? MTTR, or Mean Time to Recovery/Repair, is a crucial metric in software delivery for several reasons: OK, so what is MTTD and why does it matter? MTTD stands for Mean Time To Detect. This is a measure of how long it takes, on