Scrum and Kanban are both iterative work systems that rely on process flows

and aim to reduce waste. However; there are a few main differences between

the two:
Kanban Scrum

There are no pre-defined roles for a Each team member has a

team. Although there may still be a predefined role, where the Scrum
Roles & Project Manager, the team is master dictates timelines, Product
Responsibilities encouraged to collaborate and chip in owner defines goals and objectives
when any one person becomes and team members execute the work.
overwhelmed.

Products and processes are Deliverables are determined by

Due Dates / delivered continuously on an as-needed sprints, or set periods of time in
Delivery Timelines basis (with due dates determined by the which a set of work must be
business as needed). completed and ready for review.

Uses a “pull system,” or a Also uses a “pull system” however

Delegation & systematic workflow that allows team an entire batch is pulled for each
Prioritization members to only “pull” new tasks once iteration.
the previous task is complete.

Allows for changes to be made to a Changes during the sprint are

Modifications / project mid-stream, allowing for strongly discouraged.
Changes iterations and continuous improvement
prior to the completion of a project.
 Measures production using “cycle Measures production using
Measurement of time,” or the amount of time it takes to velocity through sprints. Each sprint
Productivity complete one full piece of a project is laid out back-to-back and/or
from beginning to end. concurrently so that each additional
sprint relies on the success of the one
before it.

Best for projects with widely-varying Best for teams with stable
Best Applications priorities. priorities that may not change as
much over time.