This document compares and contrasts Scrum and Kanban frameworks. It notes that while Scrum is prescriptive with roles, timeboxed iterations, and cross-functional teams, Kanban is more flexible with its visual workflow, work in progress limits, and lead time measurement. The document provides examples of experimenting with work in progress limits in Kanban and highlights some minor differences like Scrum's prioritized backlog and daily meetings compared to Kanban.

1. Lean/Kanban – Going beyond
Scrum
Kamon Treetampinij (Korn4D)

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. 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. Scrum
Split your
organization
into small, cross-functional, self- organizing teams.

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. Scrum
Split time
into short fixed-length iterations (usually 1 – 4 weeks),
with potentially shippable code demonstrated after each iteration.

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. 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. Kanban
•
Visualize the workflow
•
Limit Work In Progress (WIP)
•
Measure the lead time

10. Scrum is more prescriptive than
Kanban

11. Scrum prescribes roles
•
Product Owner
•
Team
•
Scrum Master

12. Scrum prescribes timeboxed
iterations
Single
Cadence

13. Kanban Cadence
Three
Cadence
Event
Driven

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. Example: Experimenting with WIP limits in
Kanban

16. Example: Experimenting with WIP limits in
Kanban

17. Example: Experimenting with WIP limits in
Kanban

18. Example: Experimenting with WIP limits in
Kanban

19. Example: Experimenting with WIP limits in
Kanban

20. Scrum board is reset
between each iteration

21. Scrum prescribes crossfunctional teams

22. Scrum backlog items must fit
in a sprint

23. Scrum prescribes estimation
and velocity

24. Scrum working on multiple
products simultaneously

25. Kanban working on multiple
products simultaneously

26. Minor Differences
•
Scrum prescribes a prioritized product backlog
•
In Scrum, daily meetings are prescribed
•
In Scrum, burndown charts are prescribed

27. Look at the charts

28. One day in Kanban-Land

29. One day in Kanban-Land

30. One day in Kanban-Land

31. One day in Kanban-Land

32. Reference
http://www.infoq.com/minibooks/kanban- scrumminibook
http://bit.ly/kanbanbk
k

33. “There is no dumb questions.”

34. See you again at