Recommandé
Contenu connexe
Plus de Skills Matter
Plus de Skills Matter (20)
Dernier
Dernier (20)
Myfirstkanban
- 1. My First Kanban Erling Wegger Linde
- 2. @erlingwl
- 4. Context
- 5. Process .. -> In dev -> Ready For Review -> Done -> ..
- 6. Motivation .. -> In dev -> Ready For Review -> Done -> ..
- 7. Introducing Kanban 10 .. -> In dev -> Ready For Review -> Done -> ..{ Limit WIP Visualize Pull Flow
- 8. How we sold it Wq = Lq/λ +
- 9. Evolving 10 10 .. -> Ready For Dev -> In dev -> Ready For Review -> Done -> .. { {
- 11. Distributed Team
- 13. Always look at the whole
- 14. How I hoped it would evolve 5? 10? 8? 5? Idea -> Analysis -> Development -> Testing -> In production
- 15. Questions? • http://erlingwl.wordpress.com/ • @erlingwl • http://uk.linkedin.com/in/erlingwl
Notes de l'éditeur
- 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