software delivery

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

Team members software delivery

Frequent vs Infrequent software releases / delivery

by

I’ve previously worked at banks which released veryyyyyy infrequently. I’m talking quarterly or half year windows. Releases are a big fucking deal over there because if you can’t release you gotta wait for the next window a few months down road (awful I know). However, sometimes there’s a specific reason why banks or old organizations function that way. The world’s best software teams tend to release software more frequently. This approach allows them to be more agile, responsive to user feedback, and maintain a competitive edge in the market. These teams often adopt Agile methodologies, DevOps principles, and Continuous Integration/Continuous