1.3. What is the Kanban Method?
As Taiichi Ohno introduced the theory into the manufacturing industry, David J. Anderson was responsible for applying the concept to IT, Software Development and Knowledge work in general in 2004. David modified the inventions of Taiichi Ohno, Eki Goldratt, Edward Demmings, Peter Drucker and others to define the Kanban Method, with perceptions like pull systems, queuing theory and flow. His first book on Kanban – “Kanban: Successfully Evolutionary Change for your Technology Business”, published in 2010, is the most comprehensive classification of the Kanban Method for knowledge work.
The Kanban Method is a structured system to progressively improve whatever you do – whether it is software development, IT/ Ops, Staffing, Recruitment, Marketing and Sales, Procurement etc. As a matter of fact, almost any business function can profit from applying the principles of the Kanban Methodology.
The Kanban body of knowledge has abstracted and benefited from the works of various thought leaders since the original book was written! People such as Don Reinertsen (author of Principles of Product Development Flow), Jim Benson (pioneer of Personal Kanban) and several others.
“Kanban is not a software development lifecycle methodology or an approach to project management. It requires that some process is already in place so that Kanban can be applied to incrementally change the underlying process.” – David J. Anderson