4 ms·

From TFA: David Anderson, the creator of The Kanban Method (discussed above) wrote the following in late 2010. “Kanban is NOT a software development lif

From TFA: David Anderson, the creator of The Kanban Method (discussed above) wrote the following in late 2010. “Kanban is NOT a software development life cycle or project management methodology! It is not a way of making software or running projects that make software!”

agileramblings 13y ago
Unfortunately, the tendency to overload terms with multiple meanings is confusing the situation. It is very common for the word kanban to be used incorrectly because there are three commonly confused meanings for the word. kanban - visual signal, signboard kanban system - pull-based, wip limited flow management system Kanban Method - an approach to incremental, evolutionary process and systems change for organizations So yes, the Kanban Method is not an SDLC method. It is a meta-method that will allow for the emergence of an appropriate SDLC within an organization. That SDLC may be Agile (very good things in Agile mindset), may be waterfall, may be Scrum or Scrumban-ish, but it should be appropriate for then context. Please refer to this wikipedia entry: http://en.wikipedia.org/wiki/Kanban_(development) http://en.wikipedia.org/wiki/Kanban_(development) You don't see any SDLC specific tactics or guidance in there. That is true. You don't see any Agile language in there. It doesn't provide any specific Agile guidance. Does the Agile Manifesto have any specific SDLC tactics? Please refer to http://www.agilemanifesto.org http://www.agilemanifesto.org You won't find any specific tactics for software development in the Agile Manifesto either. But out of the mindset comes specific SDLCs that are aligned to the manifesto like Scrum or XP or any of the million "custom" Agile methodologies that have no name but are used by IT organizations everywhere. David Anderson absolutely wants the Kanban Method to be used (as appropriate) in organizations that do knowledge work (software development is knowledge work) to help those organizations develop the best workflow and capability for a given context and to create a culture of learning, growth, and continuous improvement. I've talked to him many times about these very topics! Many of the case studies that we quote in our work are from software development organizations. The quote used above has been taken out of context, isolated, and used to create fear, uncertainty and doubt about The Kanban Method and I find that kind of behaviour negligent at best.

agileramblings 13y ago

Unfortunately, the tendency to overload terms with multiple meanings is confusing the situation. It is very common for the word kanban to be used incorrectly because there are three commonly confused meanings for the word. kanban - visual signal, signboard kanban system - pull-based, wip limited flow management system Kanban Method - an approach to incremental, evolutionary process and systems change for organizations So yes, the Kanban Method is not an SDLC method. It is a meta-method that will allow for the emergence of an appropriate SDLC within an organization. That SDLC may be Agile (very good things in Agile mindset), may be waterfall, may be Scrum or Scrumban-ish, but it should be appropriate for then context. Please refer to this wikipedia entry: http://en.wikipedia.org/wiki/Kanban_(development) http://en.wikipedia.org/wiki/Kanban_(development) You don't see any SDLC specific tactics or guidance in there. That is true. You don't see any Agile language in there. It doesn't provide any specific Agile guidance. Does the Agile Manifesto have any specific SDLC tactics? Please refer to http://www.agilemanifesto.org http://www.agilemanifesto.org You won't find any specific tactics for software development in the Agile Manifesto either. But out of the mindset comes specific SDLCs that are aligned to the manifesto like Scrum or XP or any of the million "custom" Agile methodologies that have no name but are used by IT organizations everywhere. David Anderson absolutely wants the Kanban Method to be used (as appropriate) in organizations that do knowledge work (software development is knowledge work) to help those organizations develop the best workflow and capability for a given context and to create a culture of learning, growth, and continuous improvement. I've talked to him many times about these very topics! Many of the case studies that we quote in our work are from software development organizations. The quote used above has been taken out of context, isolated, and used to create fear, uncertainty and doubt about The Kanban Method and I find that kind of behaviour negligent at best.