Evolutionary Change thru Kanban

David J. Anderson is credited with the first implementation of a Kanban process for software development, in 2005. David leads a management consulting firm focused on improving performance of technology companies. He has been in software development nearly 30 years and has managed teams on agile software development projects at Sprint, Motorola, Microsoft, and Corbis.

David was a founder of the Agile movement through his involvement in the creation of Feature Driven Development. He was also a founder of the Agile Project Leadership Network (APLN), a founding signatory of the Declaration of Interdependence, and a founding member of the Lean Software and Systems Consortium. He moderates several online communities for lean/agile development.

He is President of David J. Anderson & Associates, based in Sequim, Washington, a management consulting firm dedicated to improving leadership in the IT and software development sectors. Last year he authored the defining book on Kanban: Successful Evolutionary Change for Your Technology Business.

Download Podcast: Click and choose options: Anderson-Kanban or go to the Business901 iTunes Store.

Kanban is becoming a popular way to visualize and limit work-in-progress in software development and information technology work. Teams around the world are adding kanban around their existing processes to catalyze cultural change and deliver better business agility. This book answers the questions: What is Kanban? Why would I want to use Kanban? How do I go about implementing Kanban? How do I recognize improvement opportunities and what should I do about them?

As a pioneer in the agile software movement David has managed teams at Sprint, Motorola and Corbis delivering superior productivity and quality. At Microsoft, in 2005, he developed the MSF for CMMI Process Improvement methodology – the first agile method to provide a comprehensive mapping to the Capability and Maturity Model Integration (CMMI) from the Software Engineering Institute (SEI).

His first book, Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results, published in 2003 by Prentice Hall, and introduced many ideas from Lean and Theory of Constraints in to software engineering. David can be found at AgileManagement.net

Related Information:
Kanban, could we call this podcast anything else?
Lean Kanban lessons from a Software Developer
Marketing Kanban
Kanban too simple To be Effective?