Kanban (capital-K, as in the method) uses a kanban (lowercase-k, as in the board) to visualise and reduce work in progress (WIP for short). This is the most well-known, and visible, part of Kanban. It is achieved by limiting how many pieces of WIP any one work centre can have assigned. At first glance, this may seem to be incompatible with IT support work. This is as erroneous as assuming Kanban is incompatible with knowledge work in general, whereas it has been proven to be an excellent match for software development (for details, I recommend David Anderson’s book “Kanban: Successful Evolutionary Change for Your Technology Business”).
Author: David J. Anderson
Publisher: Blue Hole Press
A while back, a friend of mine tipped me off to this book, and said it was a book I should read. Here are my thoughts.
A while back, I participated in a discussion about the application of Kanban in an IT Operations setting. Here are some of my thoughts on the matter: