Turning the crank
Now that we have a plan, we get to do the fun part. We get to turn the crank and do the work. We pull the next task, write the code, push it to production, and see the fruits of our labor. Right?
Actually, up to this point, the process has been very flexible. It has been a lot of talk, sticky notes, and diagrams. It has been flexible on purpose—because we are experimenting.
But now, the rubber meets the road, so to speak, and we have to get serious. After all, programming languages are notorious for doing exactly what we tell them to do, and we are about to deploy a change to production while the users are actually using the system.
So, this small part of the process needs due diligence. We call it task branch workflow. This workflow governs how we turn the crank and do the work. It includes both automated and manual gates. But it is a straightforward workflow that becomes second nature since we do it many times a day, day after day.
And it is...