software delivery

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

Bill_team_members_with_a_whiteboard_and_code_in_the_back

Velocity vs Throughput – What’s the difference?

by

In the context of software delivery, velocity and throughput are two performance metrics used to measure the effectiveness and efficiency of a development team. They help stakeholders and teams understand the progress and productivity of software development processes. While both metrics provide valuable insights, they have different focuses and should be used for different purposes. In order to understand velocity, you need to understand story points as well. Story Points: Velocity: Throughput: When to use Velocity vs Throughput over the other: Downsides to velocity/story points in software delivery: Overall, both approaches have their pros and cons, and teams should choose