What a waste

Slow software delivery processes are such a waste.

The team is made up of several highly skilled developers. Each with a unique specialty. One is an encryption expert. Another knows all about distributed computing. Not one has less than 8 years relevant technical experience.

A new feature request comes in. The team discusses a number of possible approaches, and quickly settles on the chosen course. For the next few hours, the team works the problem together brilliantly.

Not only have they built a fabulous new feature, they have full confidence in the solution, because they’ve built it along with all the necessary unit and integration tests, and all existing regression tests pass, too.

So with much joy, they merge this amazing new feature into main… and…

..they wait 3 months to see if anyone actually uses it.

What a waste.

Share this

Related Content

Talking DevOps, Go and Continuous Delivery in Reverse on the Lovin' Legacy podcast

I join the Lovin' Legacy podcast to talk about DevOps, the Go language, and implementing Continuous Delivery in reverse. Have a listen.

Talking Continuous Delivery on The Agile Embedded podcast

I join the Agile Embedded podcast to discuss continuous delivery, and how to implement it in reverse.

Who cares if we use GitFlow?

GitFlow vs Trunk-Based Development is like Coke vs. Pepsi, right? Not really.