Scrum vs Kanban | Difference Between Scrum And Kanban | Agile Methodology | Simplilearn

2. What Is Scrum? • Scum is a framework that helps teams collaborate when it comes to complex project/ products

3. What Is Scrum? • Scum is a framework that helps teams collaborate when it comes to complex project/ products • It helps teams learn from their experiences, organize themselves while working on problems, reflect on the victories and losses to help them improve

4. Click here to watch the video

5. Transition slide for How does it work – scrum How Does it Work?

6. How Does it Work? ProductBacklog

7. How Does it Work? SprintPlanning ProductBacklog

8. How Does it Work? Sprint Backlog SprintPlanning ProductBacklog

9. How Does it Work? Daily Scrum Sprint Backlog SprintPlanning ProductBacklog Scrum Team

10. How Does it Work? Sprint Retrospective Daily Scrum Sprint Backlog Sprint Review SprintPlanning ProductBacklog Scrum Team

11. How Does it Work? Sprint Retrospective Daily Scrum Sprint Backlog Sprint Review SprintPlanning ProductBacklog Increment Scrum Team

12. Transition slide for What is Kanban What is Kanban?

13. What Is Kanban? • Kanban or ‘Kamban’ in Japanese, which translates to ‘signboard’ is visual system that is used for managing work as it goes through the process 看板

14. What Is Kanban? • Kanban or ‘Kamban’ in Japanese, which translates to ‘signboard’ is visual system that is used for managing work as it goes through the process • Kanban can help determine bottlenecks, and then fix them in a cost-effective manner and optimal speeds. This is done with the help of a Kanban board.

15. What Is Kanban? • Kanban involves having work being split into pieces, and the work is item is written on a note/card and put on a board • The columns help illustrate where each item is in the workflow

16. Transition slide for How does it work – Kanban How Does it Work?

17. How Does it Work? To-do Ongoing Done

18. Transition slide for How are they similar How Are They Similar?

19. How Are They Similar? The work is broken in pieces Reduces Work in Progress Both use pull scheduling Lean and Agile

20. How Are They Similar? Releasable software are delivered often and early Transparency drives process improvement The release plan is optimized continuously

21. Transition slide for scrum vs kanban Scrum vs. Kanba

22. Scrum vs. Kanban Cadence Scrum The process is divided into time-constrained iterations

23. Scrum vs. Kanban Cadence Scrum Kanban Event-driven, instead of timeboxed The process is divided into time-constrained iterations

24. Scrum vs. Kanban Release Methodology Scrum Releases take place at the end of each sprint

25. Scrum vs. Kanban Release Methodology Scrum Kanban Releases take place in the form of continuous delivery Releases take place at the end of each sprint

26. Scrum vs. Kanban Changes Scrum Changes cannot be made during the sprint

27. Scrum vs. Kanban Changes Scrum Kanban Changes cannot be made during the sprint Changes can be made at any time

28. Scrum vs. Kanban Metric Scrum Velocity is the default metric used in planning and process improvement

29. Scrum vs. Kanban Metric Scrum Kanban Velocity is the default metric used in planning and process improvement Lead time is the default metric used for planning and process improvement

30. Scrum vs. Kanban Teams Scrum Cross-functional teams are a mandatory requirement

31. Scrum vs. Kanban Teams Scrum Kanban Specialist teams are required, and cross-functional teams are optional Cross-functional teams are a mandatory requirement

32. Scrum vs. Kanban Adding new items Scrum Items cannot be added in between an iteration

33. Scrum vs. Kanban Adding new items Scrum Kanban New items can be added, if there’s capacity available Items cannot be added in between an iteration

34. Scrum vs. Kanban Job Roles Scrum • Has 3 major job roles: • Product owner • Scrum master • Scrum Team

35. Scrum vs. Kanban Job Roles Scrum Kanban • Has 3 major job roles: • Product owner • Scrum master • Scrum Team Specific job roles haven’t been set up

36. Scrum vs. Kanban Representation Scrum The Scrum board needs to be reset after each sprint

37. Scrum vs. Kanban Representation Scrum Kanban The Kanban board stays persistent throughout the project The Scrum board needs to be reset after each sprint

38. Scrum vs. Kanban Project Length Scrum It is better suited for long running projects

39. Scrum vs. Kanban Project Length Scrum Kanban Kanban works better for projects that are expected to finish in a shorter period It is better suited for long running projects

40. Transition slide for Which to choose Which To Choose?

41. Which To Choose? Scrum

42. Which To Choose? Kanban

43. Which To Choose? Kanban