I was throwing some shapes on Twitter recently about some concerns I have with the current Kanban craze. Unfortunately I think the cursed 140 character limit meant my points got misinterpreted and may have lead people to think I’m anti-Kanban which is not the case in fact it’s quite the opposite. I’ve been using Kanban boards for over a year and half and jointly ran a presentation at XPDay2008 on evolving from Scrum to Lean which focused heavily on the use of Kanban boards.
The thing that’s making me itchy is how Kanban has somehow been elevated into a methodology unto itself. We don’t have “Scrum and Sprint” conferences or XPandPairProgrammingDay so why do we have Lean Kanban Conference Miami or the UK Lean and Kanban Conference? Also, pretty much everywhere you see someone talking about Lean software development the title of the blog or presentation also includes Kanban in the same breath? More than that I see a lot of discussion around Kanban in blog posts and Twitter but very little on Lean or the Lean Software Development principles.
I’m sure proponents of Kanban will say no one is suggesting Kanban is a methodology and I would agree I’ve not seen anyone say it is. The problem is interpretation. People have a habit of focusing on rules and methodologies because they’re a lot more easy to tackle than the problems they we’re created to solve. Scrum has been enormously successful (if you consider wide adoption a measure of success) but very few teams are doing it well as James Shore has been writing eloquently about recently because it does not force you address the real issues. The beauty of Lean software development is it is just a set of principles. It intentionally avoids prescribing how to do something. Obviously this causes problems as most people don’t want to get involved in the difficult stuff they just want to be told how to do it. Consider this reply I received on Twitter:
erwilke @robbowley “I think we’re trying to avoid kanban being seen as a stand-alone methodology, but people don’t “get” it as a set of tools”.
Maybe there’s a good reason why people don’t get it – because it you need to understand where it’s coming from. Focusing on Kanban and ignoring all the rest however, that’s easy!
Elevating Kanban to the prominent position it is now in makes me feel like history is going to repeat itself. I prophesied this some months back. It has been the most popular post on my blog by a long way.
If you’re getting into Kanban, be warned. Kanban is just a tool and in my opinion no more important than say, pair programming, unit testing or domain driven development. It is certainly a lot less important than the white elephant in the room which very few people seem to be addressing which is building the right thing in the first place. As Peter Drucker famously said: “There is nothing so useless as doing efficiently that which should not be done at all”.
Kanban is a small part of something much, much bigger, see the whole.
*Edit* Some responses to this article:
Is Kanban Just a Tool?Â – David Anderson
It is Not What It is that ReallyÂ MattersÂ -Â Israel Gat
Kanban: It’s a Tool, and There’s No Such Thing as “Just” a ToolÂ – Project Management Revolutionary
Pingback: It is Not What It is that Really Matters « The Agile Executive
I understand the issue you have with Kanban being called a methodology, but why pick on Kanban? Just because it is popular? Scrum is (as it’s proponents say) not a methodology either.
I propose that the discussion about Kanban or Scrum being (or not) a methodology is largely irrelevant. What matters is understanding in what circumstances Scrum/Kanban or other tools/methods/frameworks work and fail.
Do you have patterns or anecdotes (waiting to be developed into patterns) that shed insights into why these methods/tools/frameworks fail?
I’m not “picking” on Kanban I’m simply trying to suggest that all the problems that have come from Scrum being misinterpreted (the ability to avoid dealing with the real issues by focusing on processes and rules) are going to be the same for Kanban if it’s separated from the underlying principles of Lean. I guess that is the pattern – tools without principles are ineffective.
I never meant to get embroiled in a debate about what is and isn’t a methodology, that’s not the point I was trying to make. In hindsight I should have chosen my words more carefully.
I agree with you that tools without principles cause more problems than they solve (Cargo Cult, etc.).
Maybe we should start writing more about the principles that justify the use of Kanban (the tool).
I’ll try to come up with something on my blog as well…
Kanban is a tool, but it’s a tool that enables higher productivity. It isn’t magic, and it doesn’t create new skills or new production — but it knocks down lots of barriers.
Pingback: A Kanban Is Just A Signal To Do Work - new ThoughtStream("Derick Bailey"); -
Pingback: links for 2009-09-12 « Csom Gyula Blogja
One interesting thing is Kanban as a technique with a physical board allows viualization around things such as value mapping, pull systems, queing that makes it central to getting started. It makes a nice intro into Lean and Agile thinking as you learn by doing and its entry is very low barrier. Just my 2 cents…
Agreed. some times if a tool or a project gets more popularity and its too good ot be used by many people then it is been considered as Mehtodology.
Also agree. Kanban is just a tool, but for me quite powerful one. It eliminates lots of barriers and forces the work to flow. I’m using http://kanbantool.com