Difference between Agile Scrum and Kanban

(Q). Difference between Agile Scrum and Kanban?

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 2-4 weeks.

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.

	Kanban	Scrum
Role and Responsibilities	There are no pre-defined roles for a team. Although there may still be a Project Manager, the team is encouraged to collaborate and chip in when any one person becomes overwhelmed.	Each team member has a predefined role, where the Scrum master dictates timelines, Product owner defines goals and objectives and team members execute the work.
Due Dates / Delivery Timelines	Products and processes are delivered continuously on an as-needed basis (with due dates determined by the business as needed).	Deliverable are determined by sprints or set periods of time in which a set of work must be completed and ready for review.
Why Use?	Kanban methodology is designed to meet minimal resistance. So, it allows continuous small incremental and evolutionary changes to the current process. It also helps to achieve improvements regarding throughput, lead time and quality.	Scrum methodology can offer project management for every business, and even across life in general. By using Scrum, the development team becomes more Agile and discovering how to react quickly and respond to the sudden changes.
When to use?	Kanban boards allow visual management of software development project work. This helps team members to see work in progress. It also helps them to understand complex information like processes and risks associated to complete work on time.	Scrum methodology is used in a project where the requirement is rapidly changing. It works on a self-organizing, cross-functional team principle. The Scrum Framework usually deal with the fact that the conditions are likely to change quickly or most of the time not known at the start of the project.
Modifications / Changes	Allows for changes to be made to a project mid-stream, allowing for iterations and continuous improvement prior to the completion of a project.	Changes during the sprint are strongly discouraged.