This page is being used to gather myths of Kanban that people have heard.

The following are myths of Kanban discussed in the parent page Myths of Kanban:

• Lean Development is a prescriptive approach to work in social systems
  
• Kanban suggest linear work and requires too many handoffs
  
• Explicit policies are static, hard to change and/or inflexible
• Kanban has been successful because it is being done by early adopters
• Better to start with Scrum and then start with Kanban
  
• Kanban doesn't respect people as much as other agile methods
  
• Kanban doesn't attend enough to people
  
• To make great changes you need to be revolutionary while Kanban is evolutionary

Here are some other myths, not included on that page:

• Kanban is Scrum without iterations
• Kanban is mostly good for support
• Kanban results in teams not changing
• Kanban cannot work because explicit policies make no sense in the Agile world
  

If you see another myth that isn't up here, please send an email to alshall @ netobjectives.com and tell me about it. You can also send me an email just to tell me about ones you've found particularly prevelent.

Thanks for your help.

Al Shalloway