At some point in your career, you are going to run into a software release that is either teetering on the brink or has gone completely off the rails. Not everyone will know there is something wrong, but you will, it will be gnawing at you in each and every status meeting, with each discussion on who is working on what, with every bit of confusion that you see with the team you will come to the conclusion that yes — this release is broken.
There might be those on your team that might feel the same way (and possibly know it for a fact) but will hide behind the familiar refrain — “we can’t stop and do nothing, we have to keep fixing it along the way”.
Have you ever seen someone change a tire while the car is barrelling down the highway?
Me neither.
You need to stop it, to change the tire, so it can get back on the road, and this is where we start.
Stop What You’re Doing
You know there is a problem, so now it’s time for everyone to stop what they are doing and investigate what that problem is. This doesn’t have to be some great massive proclamation at your next stand-up, it’s simply getting the key people together and making them aware of what will happen if you keep on this path.
