Upendra 
Scrum vs Kanban
Scrum
Scrum is an agile process that helps to deliver the business value in the shortest time. It rapidly and repeatedly inspects actual working software. It emphasizes on teamwork and iterative progress of the software. Its goal is to deliver new software every 1-4 weeks.
Kanban
Kanban is a visual system for managing work. It visualizes both the process and the actual work passing through that process. The main objective of implementing Kanban is to identify potential bottlenecks in the process and fix them. Kanban goal is that work flow should proceed smoothly at an optimal speed.
Conclusion
| Scrum | Kanban |
|---|---|
| Scrum stresses on planning. It starts with sprint planning and ends up with sprint retrospective. | Kanban is open to making changes on the go. It means there is less rigidity and things can change frequently. |
| It recommends collection of time measurements made during sprints | Kanban recommends graphs to get an overview of team’s progress over time. |
| Estimation has a very important role in Scrum | No mandatory requirements for estimation. |
| Every individual has their role and responsibilities. | No set roles so flexibility in term of individual responsibilities. |
| It is not possible to add items to ongoing iterations. | New items can easily add if the additional capacity is available. |
| Measures production using velocity through sprints. | Measures production using cycle time or the exact time it takes to complete one full piece of a project. |
Links
https://www.guru99.com/scrum-vs-kanban.html
https://kanbanize.com/blog/kanban-vs-scrum-infographic/
https://perfectial.com/blog/scrum-and-kanban-are-they-different/
Opps - concurrency