Kanban is a method for developing software products and processes with an emphasis on just-in-time delivery while not overloading the software developers. It emphasizes that developers pull work from a queue, and the process, from definition of a task to its delivery to the customer, is displayed for participants to see.
The Kanban method is an approach to incremental, evolutionary process change for organizations.
One of the key Lean principles is Flow – creating a continuous and predictable delivery stream of Features/Capabilities. Kanban visualizes the Features/Capabilities currently queued and in process, and employs mechanisms aimed at minimizing flow disruptions, wasted effort, and amount of in-process inventory.
Activities, Issues and Impediments rise to the surface and are dealt with rather than swept under the carpet.
Limiting the Work in Process (WIP) encourages key behaviours desired in Lean/Agile environments, e.g.,
A rigorous Continuous Improvement regimen encourages removal of Systemic Causes of Problems. Retrospectives, Operational Reviews, Advanced analytics based on Lean, Six Sigma and Queueing Theory Science, all contribute to systemic study and improvement of process performance.
Kanban can visualize and manage any kind of workflow, usingsemantics such as “Work Types”, “Classes of Service”, “Horizontal SwimmingLanes”, “Tagging”, “Hierarchical Work Types”.
Kanban is used by a wide range of organizations – small, medium and large.