Managing work — Part V — Small increments

My favorite way to work and deliver value is by using small increments. Such as working on one item at a time and making sure to deploy it to production before picking up new work.

This post is about a story in 3 acts that shows how this guiding principle was somehow put to the test by my team last week.

The intent is to make fun of what deploying small increments means and bring to my teammates' attention that too many things in progress are no good.

Nothing happened, by the way, and everything went into production seamlessly. Still, I hope I've been able to pass the message that thinking about how much impact big releases have is always very important.

Act one

Act two

Act three