Do less rework
September 7, 2021By working in smaller iterations, we don't just re-organize our work, we actually reduce the amount of work we do.
The strongest correlation was seen in the precentage of time spent on rework or unplanned work, including break/fix work, emergency software deployments and patches, responding to urgent audit documentation requests, and so forth.
So in essense, by working in smaller iterations, and seeing those iterations through to the end before picking up a new task, we don’t just re-organize our work, we actually reduce the amount of work we do.
I guess that might be intuitive at some level. But there are enough dots to be connected, that I think it’s worth pointing out explicitly, and I’m quite glad that authors Nicole Forsgren, PhD, et al, took the time to do the statistical analysis to show conslusively that this is how things work.
Don't deploy on payday!
Blocking deployments on certain days is an admission that standards are lower every other day.
A GitFlow story
A team I recently started working with has been using GitFlow. Until last week.
How to handle long-running batch jobs during an upgrade
Two approaches to managing hours-long jobs with continuous deployment.