Importance of Kanban work-in-progress (WIP) limits

Charan/ January 16, 2011/ Agile

Traffic Jams! For some it is the bane of driving. Accidents, construction, reduced speed zones are all some of the root causes. But did you know of Phantom Traffic Jams? For no apparent reason the traffic slows to a crawl. No accidents or lane closures and there is no easy way out. Researchers have linked such phantom traffic jams to traffic density and variations in driver behavior. A trivial reason such as a driver braking too hard, can cause a phantom traffic jam 8 to 10 kms behind. And this traffic jam takes a life of its own. You could spend hours within that jam. So what does phantom traffic jams have to do with WIP limits on Kanban for software development?

Lean software development using Kanban

Charan/ January 13, 2011/ Agile

Kanban is a Japanese term that literally means “signboard”. in its strictest sense, it is essentially a scheduling system that “signals” what to produce, when to produce and how much to produce. As you will see, Kanban is a pull system. Work gets pulled by the people who actually do the work based on their availability. Kanban can lay over your existing process and asks you to follow just three basic principles:
Visualize your workflow, limit your work in progress, and only start new work when you have finished some existing work.