Keeping people busy

The Kanban Guide talks about optimizing the workflow for three different attributes: effectiveness, efficiency, and predictability. It talks about the fact that any optimizations we perform will be a balance across these three and that over-optimizing on one may make the others worse.

Steps to improving predictability

If you have a need to know when the work will be done or how much you can do in a certain period of time then predictability will be important to you. We have great tools like monte carlo for probabilistic forecasting but the truth is that the forecast we generate is only as good as the data we give it. Garbage in yields garbage out. So how do we improve our data to make it inherently more predictable?

Optimizing collaboration

A manager at a past client of mine once had a new request come in. The new request would impact multiple different teams, that would all have to make changes to their individual pieces and then integrated. Because it was potentially a large change, he asked all the teams involved to come up with an estimate and they came back with a total estimate of ten to twelve weeks.

Technical Debt

The term “technical debt” is widely used in the industry even if there isn’t a clear definition of it and almost nobody uses the term in the way Ward Cunningham meant when he first coined it. It’s most commonly used to describe things in our environment, usually but not always code, that slow us down. These are things that are working - not bugs - but that are implemented in a poor way that makes them more difficult to understand or modify.

Multiple boards for a single team

Many teams assume that they have to fit all their work on to one board and that’s not true. Kanban boards are there to help you visualize and manage the system. If one board can do that well then one board is fine. If it would be easier or better to visualize and manage across multiple boards then that’s what you should do.

Who should define the workflow?

We regularly talk about optimizing the workflow but we don’t talk as often about who should be doing that optimization. Should it be the manager, or some dedicated process specialist, or should we be leaving it up to the team to figure out their own workflow?

One Thing vs Multiple Things

When creating a forecast first ask yourself whether you are forecasting One Thing or Multiple Things. It’s not always clear which of these situations you are in but the approach you take to creating the forecast will differ significantly. This post will help you to figure out which approach to take.

Defining a workflow

The Kanban Guide defines three core practices. The first is “define and visualize a workflow” and while it describes what needs to be in that workflow, it doesn’t give any guidance on how to facilitate as session with a team to do that definition. In this video, I describe how I facilitate a session with teams to define their workflow.

Staying within our WIP limits

In a Kanban model, one thing we find most teams struggle with are WIP limits. Everyone wants to just start one more item even if we’re already at the limit. Surely one more can’t hurt. Except of course, it does.