Kanban

3,370
-1

Published on

Kanban is more and more popular approach among teams working on building software. At the same time it is probably the most light-weight approach which is applicable in such cases. What exactly Kanban is? How does it work? When, where and why it is worth to adopt it?

The session describes basic rules of Kanban and explains when the method, or its elements, is worth applying in software development teams. Comparisons to both: formal approaches and agile methods, with special focus on Scrum, help to understand Kanban specifics and learn when it might be a suitable option for teams.

Published in: Technology, Business

Kanban

  1. 1. Kanban Paweł Brodzinski @pawelbrodzinski
  2. 2. About me VSoft http://vsoft.pl Bloghttp://blog.brodzinski.com Twitter @pawelbrodzinski
  3. 3. Where is Kanban from?
  4. 4. PRIORITY ID DUE DATEKanban: ITEM NAME DATE FROM DATE TO
  5. 5. Kanban is an approach to changemanagement. It isn’t a softwaredevelopment or project managementlifecycle or process. David Anderson
  6. 6. Kanban Visualize workflowLimit WIP (Work In Progress) Manage flow Make policies explicit Improve collaboratively
  7. 7. Kanban Start with what you have Agree to pursue incremental, evolutionary changeRespect current environment (process, responsibilities, roles, etc.)
  8. 8. Scrum versus Kanban
  9. 9. Scrum versus Kanban TeamSM PO TEAM
  10. 10. Scrum versus Kanban Process
  11. 11. Scrum versus Kanban Time boxing/cadenceRelease Retro Planning
  12. 12. Kanban Start with what you have Agree to pursue incremental, evolutionary changeRespect current environment (process, responsibilities, roles, etc.)
  13. 13. Kanban + PMBOK?
  14. 14. Kanban Visualize workflow Limit WIP Manage flow Make policies explicitImprove collaboratively
  15. 15. World steering center
  16. 16. The simplest Kanban board TO DO ONGOING DONE 2
  17. 17. Kanban boardBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  18. 18. Hand-offsBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  19. 19. Who does what?BACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  20. 20. BlockersBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  21. 21. Classes of serviceBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  22. 22. ID WORK ITEM
  23. 23. PRIORITYID DUE DATE ITEM NAMEDATE FROM ESTIMATEDDATE TO SPENT SIZE
  24. 24. Kanban Visualize workflow Limit WIP Manage flow Make policies explicitImprove collaboratively
  25. 25. BACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  26. 26. Kanban Visualize workflow Limit WIP Manage flow Make policies explicitImprove collaboratively
  27. 27. Why WIP limits? 5O
  28. 28. How to set limitsBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE ? ? DONE ONGOING ?DONE ONGOING ? L
  29. 29. WIP limits different wayBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE ONGOING DONE ONGOING DONE L
  30. 30. Kanban Visualize workflow Limit WIP Manage flow Make policies explicitImprove collaboratively
  31. 31. BACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L WIP
  32. 32. START HERE
  33. 33. You need team buy-in
  34. 34. Value stream mapping
  35. 35. Upstream/downstream process TO DO ONGOING DONE 2
  36. 36. Upstream/downstream processBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  37. 37. The simpler the better
  38. 38. One or many boards?
  39. 39. Alternative Kanban board designs
  40. 40. Kanban Visualize workflow Limit WIP Manage flow Make policies explicitImprove collaboratively
  41. 41. What’s in it for me?
  42. 42. Everyday informed decisionsBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  43. 43. Behavior changesBACKLOG TO DO DEVELOPMENT TESTING DEPLOYMENT DONE 2 3 DONE ONGOING 3 DONE ONGOING 2 L
  44. 44. Best engineering practices
  45. 45. Continuous improvement
  46. 46. Thank youQuestions? Paweł Brodzinski blog.brodzinski.com vsoft.pl @pawelbrodzinski
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×