Lean/Kanban – Going beyond Scrum

1,262 views

Published on

If you are interested in Agile software development, Scrum might be the first Agile methodology you have learnt. The problem is it might not fit your work environment. Let’s explore another methodology that stands the test of time. There are many people out there discovered that Lean/Kanban is more suitable for their environment than other methodologies. See, you might be one of those.

Published in: Technology, Business

Lean/Kanban – Going beyond Scrum

  1. 1. Lean/Kanban – Going beyond Scrum Kamon Treetampinij (Korn4D)
  2. 2. About myself Agile coach with more than 10+ years of hands-on experience in the industry including the rare and repetitive success cases of self-managed team building in both local and international enterprises
  3. 3. Scrum is good but … • We are support team • We keep failing our sprint • The scope is changing every day • The story is longer than a sprint • We have architect team • Etc.
  4. 4. Scrum Split your organization into small, cross-functional, self- organizing teams.
  5. 5. Scrum Split your work into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item.
  6. 6. Scrum Split time into short fixed-length iterations (usually 1 – 4 weeks), with potentially shippable code demonstrated after each iteration.
  7. 7. Scrum Optimize the release plan and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration. Optimize the process by having a retrospective after each iteration.
  8. 8. So, for Scrum Instead of We have • Large group • Small team • Spending a long time • Spending a short time • Building a big thing • Building a small thing
  9. 9. Kanban • Visualize the workflow • Limit Work In Progress (WIP) • Measure the lead time
  10. 10. Scrum is more prescriptive than Kanban
  11. 11. Scrum prescribes roles • Product Owner • Team • Scrum Master
  12. 12. Scrum prescribes timeboxed iterations Single Cadence
  13. 13. Kanban Cadence Three Cadence Event Driven
  14. 14. Kanban limits WIP per workflow state, Scrum limits WIP per iteration So in Scrum WIP is limited per unit of time. In Kanban WIP is limited per workflow state.
  15. 15. Example: Experimenting with WIP limits in Kanban
  16. 16. Example: Experimenting with WIP limits in Kanban
  17. 17. Example: Experimenting with WIP limits in Kanban
  18. 18. Example: Experimenting with WIP limits in Kanban
  19. 19. Example: Experimenting with WIP limits in Kanban
  20. 20. Scrum board is reset between each iteration
  21. 21. Scrum prescribes crossfunctional teams
  22. 22. Scrum backlog items must fit in a sprint
  23. 23. Scrum prescribes estimation and velocity
  24. 24. Scrum working on multiple products simultaneously
  25. 25. Kanban working on multiple products simultaneously
  26. 26. Minor Differences • Scrum prescribes a prioritized product backlog • In Scrum, daily meetings are prescribed • In Scrum, burndown charts are prescribed
  27. 27. Look at the charts
  28. 28. One day in Kanban-Land
  29. 29. One day in Kanban-Land
  30. 30. One day in Kanban-Land
  31. 31. One day in Kanban-Land
  32. 32. Reference http://www.infoq.com/minibooks/kanban- scrumminibook http://bit.ly/kanbanbk k
  33. 33. “There is no dumb questions.”
  34. 34. See you again at

×