Latest articles about Blockchain Gaming, esports and Agile Project Management.

Software delivery team on board

Why does MTTD & MTTR matter for software delivery?

by

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

Change failure rate

What is change failure rate and what to look for?

by

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

Software delivery room

Balancing tech debt and product needs – Why is it important?

by

It’s been a while! A few weeks ago I wrote about work in progress limits and software delivery frequency. Today, I’ll be writing about technical debt or (tech debt) and why it’s important to manage as you scale. Tech debt isn’t just a large business problem to solve. It impacts startups and mid sizes organizations just as much. Let’s start off with some basics. What is technical debt? What is technical debt? Technical debt is a concept in software development that refers to the cost of making shortcuts or suboptimal decisions during the development process, which can lead to increased