Both Kanban and Scrum are lean/agile methodologies and are highly adaptive. They are pull-based scheduling systems that enable the JIT (just in time) principle of Lean. Scrum is more prescriptive with key roles and ceremonies pre-defined. Kanban is flow-based and provides the ability to change priority at any time. Rhythm provides the ability to use either or both methodologies together.
A summary of some key differences:
| Scrum | Kanban | |
|---|---|---|
| Work Assignment |
Work is pulled into sprints in batches matching Sprint cadence. |
Work is pulled in as other work completes. |
| Dates/Delivery |
Value is delivered in staged increments (Sprints). Dates are set in advance. |
Value is continuously delivered. Due dates set as needed. |
| Change/Adjustment |
Change occurs at Sprint boundary (mid-Sprint changes are strongly discouraged). |
Since work is not pre-assigned, change can happen at any time. |
| Ideal Application |
Best with stable priority and incremental delivery. |
Projects with very dynamic content, and widely varying priority. |
| Measurements |
Velocity (average delivery per sprint). |
Cycle time (time for item throughput). |
| Government |
Capacity controlled (projected work per sprint). |
WIP (work in progress) limited. |
| Process |
Lightweight process with roles and ceremony, but still a prescriptive process. |
Easily adapted to custom workflow and process. |
Both are valid choices for managing delivery, but one may be better suited to your specific project. Feel free to experiment with your project configurations until you find the best process for your team.