What happens when people try out Kanban? (for the first time?)
Bank
Back office
Accounting rules engine
Bureaucracy
Waterfall or anarchy? We started doing XP / Scrum
By end of iteration – a lot of stories had piled up in “Ready for Review”
W (average time in the queue) = L (average number of things in the queue) / λ (average processing rate)
http://scalingsoftwareagility.wordpress.com/2009/12/14/an-agile-illusion-how-that-nice-backlog-is-actually-decreasing-your-team%E2%80%99s-agility/
Benefits and drawbacks
WIP limits needs to have buffer
However, nice when stories have been completed / reviewed over night. Works best with India handing stories over to UK..
Hard to explain Kanban to other locations.
Cultural and political differences. Some people like C&C. Personal Agendas.
Repeating message over and over again helps.
By measuring only from Ready For Dev -> Done (but done was only Done with Development) we encouraged the wrong behavior
People were splitting stories too much
People did not think all the way to production – features were essentially not working
Span the whole process
Break down silos and project boundaries
Encourage communication
