This document discusses blending SCRUM and Kanban approaches. It describes using Kanban at different levels of an organization, including at the portfolio, program, and team levels. Kanban focuses on limiting work in progress to improve flow and make bottlenecks visible. The document compares SCRUM and Kanban methods and suggests using a combination of the two by overlaying Kanban's work in progress limits on top of a SCRUM board at the team level. This allows restricting work in each column to optimal levels to increase throughput and productivity across the entire enterprise.

1. Blending
SCRUM and Kanban
to create a
Scalable Lean-Agile
Enterprise
Ravneet Kaur

4. Motivation for Kanban Method

5. Motivation for Kanban Method

6. Kanban is like flowing water

7. Kanban Philosophy

8. Kanban Philosophy

9. Little’s Law and Measuring Productivity
Kanban follows Little’s Law for measuring Productivity.
• WIP – Work In Process: The amount of material in the process of being
worked on but has not yet become a saleable product.
• Throughput: The amount of time it takes for an item to be made from
beginning its processing to its completion.
• Lead Time (Cycle Time): The amount of time it takes to do one specific
operation.

10. Little’s Law and Measuring Productivity

11. Is our goal 100% utilization

12. Is our goal 100% utilization

13. Limiting WIP (Work in Progress)
Why limiting work in
progress makes sense ?

14. Case Study
We will use a drive-thru to explain why.

15. Limiting WIP (Work in Progress)
For the complete video of the Case Study, please
click on the following link.
https://www.youtube.com/watch?v=W92wG-
HW8gg&list=WL&index=84

16. Time to move towards excellence

19. Visualise workflow with value stream mapping

20. Value stream mapping to Kanban Board

21. Kanban makes bottlenecks visible

22. Kanban helps in improving process

25. One day in Kanban Land

26. One day in Kanban Land

27. One day in Kanban Land

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. One day in Kanban Land

33. One day in Kanban Land

34. One day in Kanban Land

35. One day in Kanban Land

36. One day in Kanban Land

38. Differences between SCRUM and Kanban

39. Differences between SCRUM and Kanban

40. Differences between SCRUM and Kanban

41. Differences between SCRUM and Kanban

42. Differences between SCRUM and
Kanban

43. Differences between SCRUM and Kanban

44. Differences between SCRUM and Kanban

45. Differences between SCRUM and Kanban

46. Differences between SCRUM and Kanban

47. Differences between SCRUM and Kanban
For the complete video for Differences between
SCRUM and Kanban, please click on the
following link.
https://www.youtube.com/watch?v=Jx6_E5XxqEo

48. Kanban in SAFe

49. Kanban in SAFe
Kanban is the key ingredients for implementing
SAFe (Scaled Agile Framework).
At Portfolio Level, Kanban is recommended.
At Program Level, Kanban is recommended.
At Team Level, combination of SCRUM and
Kanban is recommended.

50. Kanban creates a Pull System across the entire
Portfolio that is limited by the Teams‘ Capacity.

52. Kanban at Portfolio Level

53. Kanban at Program Level

54. Kanban at Team Level

55. Scaling Kanban

56. Kanban at Team Level
When should we use Kanban at Team Level?
The Teams where it’s not possible to use Scrum in its complete
form. For example,
Where it’s not possible to decompose the User Stories to fit
into a Sprint.
Where it’s not possible to have time-boxed Releases (e.g.
Firmware)
Hardware Teams

57. Kanban at Team Level
When should we use Kanban at Team Level?
• During hardening sprints
• For the support / helpdesk teams / activities
• For periods of heavy R & D

58. Kanban at Team Level
When should we use Kanban at Team Level?
For the Teams where Scrum is used in its complete form.
It is highly recommended to overlay Kanban on top of Scrum by
restricting WIP to an optimal value for each of the columns in
Scrum Board.
This will result in higher throughput and helps in determining
bottlenecks and increasing overall productivity at all level of the
enterprise.
This will also result in better collaboration among the team
members.

59. Kanban at Enterprise level