Kanban Improvements
•
3 likes•1,959 views
With only a few principles which Kanban prescribes it can’t be treated as a method which directly shows how to organize a team or the way it works. What more, it is advised to start Kanban implementation without changing the process which is currently in place. How Kanban catalyzes improvements then? Basing on examples from different teams the presentation shows patterns of emergent properties – best practices and process improvements which are introduced with no direct management action. As these behaviors are emergent not only are they adjusted to local specifics but also there’s little resistance against them. This mechanism makes Kanban, despite the method’s simplicity, a great tool to foster improvements.
Recommended
Recommended
More Related Content
Viewers also liked
More from Pawel Brodzinski
More from Pawel Brodzinski (20)
Recently uploaded
Recently uploaded (20)
Kanban Improvements
- 1. Kanban improvements Emergent behavior Pawel Brodzinski @pawelbrodzinski #lkse12
- 2. Hi, I’m Pawel VSoft http://vsoft.pl Software Project Management http://blog.brodzinski.com Twitter @pawelbrodzinski
- 3. I have a few stories you... for you...
- 4. HANDOFFS
- 5. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 6. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 7. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE B H
- 8. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE B H
- 9. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B H
- 10. SWARMING
- 11. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 12. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 13. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 14. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 15. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 16. That’s not all There is more
- 17. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 18. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 19. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 20. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 21. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B N
- 23. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H
- 24. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H
- 25. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H
- 26. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H
- 28. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H
- 29. RELEASE STRATEGY
- 30. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 9 ONGOING DONE ONGOING DONE N B H
- 31. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 9 ONGOING DONE ONGOING DONE N B H
- 32. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE B H
- 33. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE B H
- 34. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE B H
- 35. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 36. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 37. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 38. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 39. ESTIMATION
- 40. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B
- 41. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B With 90% probability we will complete feature J in 18 days or less
- 42. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B WIP
- 43. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B WIP AVERAGE AVERAGE TACT TIME AVERAGE AVERAGE TACT TIME TACT TIME TACT TIME
- 44. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B WIP AVERAGE AVERAGE TACT TIME AVERAGE AVERAGE TACT TIME TACT TIME TACT TIME 10 x10
- 45. WORK ITEM ITEM SIZE DATE ADDED TO BACKLOG DATE WORK STARTED DATE WORK FINISHED
- 47. There is no prescription! prescription!
- 50. DEPLOY BACKLOG TODO DEVELOPMENT TESTING MENT DONE 2 3 2 1 ONGOING DONE ONGOING DONE H B WIP limits and pull mechanics steer behavior changes
- 53. Thank you Questions? Questions? Pawel Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski