Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Scrum or Kanban

269 views

Published on

Internal research on the topic if Kanban can be chosen over Scrum

Published in: Software
  • Be the first to comment

  • Be the first to like this

Scrum or Kanban

  1. 1. HOLLYWOO STARS AND CELEBRITIES WHAT DO THEY KNOW? DO THEY KNOW THINGS?? LET'S FIND OUT! © "Bojack Horseman" cartoon tv-show
  2. 2. SCRUM, KANBAN - FIGHT!
  3. 3. NAAAHH. LOVE, PEACE, BUBBLEGUM
  4. 4. BAD PROJECT CANNOT BE FIXED WITH A GOOD TOOL
  5. 5. DEVELOPMENT FRAMEWORKS CAN BE DIVIDED BY THE AMOUNT OF PRESCRIPTIONS THEY PROVIDE
  6. 6. SCRUM: 9 KANBAN: 3 SCRUM IS MORE STRICT KANBAN IS MORE OPEN
  7. 7. RATIONAL UNIFIED PROCESS AKA RUP 120+
  8. 8. SCRUM PRESCRIPTIONS: Role - Product Owner Role - Scrum Master Role - Team Timeboxed iterations Cross functional team Estimations and Velocity Prioritized backlog Standups Burndown chart
  9. 9. KANBAN PRESCRIPTIONS: Visualize the workflow Limit Work In Progress(WIP) Measure the lead time
  10. 10. COMMONALITIES Lean and Agile Use pull scheduling Limit WIP Transparency to drive process improvement Focus on delivering releasable software early and often Based on self-organizing teams Require breaking the work into pieces Focus on delivering releasable software early and often The release plan is continuously optimized based on empirical data (velocity/lead time)
  11. 11. DIFFERENCES
  12. 12. SCRUM BOARD
  13. 13. KANBAN BOARD
  14. 14. IN SCRUM WIP IS LIMITED PER UNIT OF TIME IN KANBAN WIP IS LIMITED PER WORKFLOW STATE
  15. 15. IN SCRUM YOU RESET YOUR BOARD EVERY SPRINT IN KANBAN YOUR BOARD IS SOLID
  16. 16. IN SCRUM YOU SUPPOSE TO HAVE CROSS-FUNCTIONAL TEAM IN KANBAN YOU CAN HAVE SPECIALIZED TEAM
  17. 17. IN SCRUM CARDS SHOULD FIT IN THE SPRINT IN KANBAN YOU CAN HAVE LONG RUNNING TASKS
  18. 18. IN SCRUM YOU OPERATE ON ESTIMATIONS AND VELOCITY IN KANBAN YOU OPERATE ON LEAD TIME
  19. 19. IN SCRUM YOU NEED TO HAVE STANDUP IN KANBAN YOU ...
  20. 20. IN SCRUM YOU NEED TO HAVE BURNDOWN IN KANBAN YOU ...
  21. 21. IN SCRUM YOU NEED TO HAVE PLANNING IN KANBAN YOU ...
  22. 22. IN SCRUM YOU NEED TO HAVE BACKLOG REFINEMENT IN KANBAN YOU ...
  23. 23. IN SCRUM YOU NEED TO HAVE RETROSPECTIVE IN KANBAN YOU ...
  24. 24. PROS (PERSONAL OPINION) Less-is-better or "Occam's razor" We are not so many people for Scrum Kanban usually fits better in non-agile environments More pair programming and team work Much shorter lead times (that one is objective) Potentially can solve PO problem by obsoleting role Some resources will be freed
  25. 25. CONS (PERSONAL OPINION) Scrum is already working for us We will need to re-establish many things We will need to drop some roles and "invent" some other roles We will need to solve PO problem somehow
  26. 26. PLEASE DO BEFORE NEXT RETRO: Read about Kanban Refresh your knowledge about Scrum Make your own research Form your opinion ... Profit!!!
  27. 27. THE END HTTPS://GITHUB.COM/KALABIYAU

×