What a waste
November 17, 2022Slow 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.
Implementing Continuous Delivery in Reverse - ATVIE22
If you heard about Continuous Delivery you might find it sounds great, but you are not ready for it because [insert excuse here].
Isn't it wasteful to build after every commit?
Continuous delivery provides some very cheap insurance.
Stop starting and start finishing
Today I installed the door on some furniture I built a year ago. Reminds me of many user stories.