I was asked a couple of days ago, what I think about KANBAN for Software development. Searching google for KANBAN development brings.
A much better article you will find here:
Knowing that the KANBAN system was used to create a flow of material to produce cars on a factory belt, I wonder why some people want to go back to production techniques developed by car makers, when they think about how to improve software development.
KANBAN was working for Toyota. Most Car makers have not been able to adapt it well. In  the autor describes that the “manager” moves the cards.
The KANBAN system used in the way it is described in  is harmful for software development because it works thinking in disciplines, comparing Analysis, Design, Impl. … with building parts is bad. It makes the waterfall thinking in our minds even stronger.