Agile: Scrum vs. Kanban

Comparison Matrix

KPITeam velocityCycle-time
GoalBuilding highly reliable and predictable teams.Building flexible and resilient teams.
Suitable ForConsistent and predictable workloads.Mid-term and long-term Deliverables. Multiple teams at scale.Unpredictable and arbitrary workloads. Short-term and high-priority deliverables. Small and independent teams.
Cadence2-Weeks Sprints3 to 5-Sprints Milestones1-Week Beats
RolesProduct Owner (PO)Scrum Master (SM)Development TeamN/A
CeremoniesPlanningDaily ScrumsReviewDemoRetro_Scrum of Scrums_Daily Stand-ups
BoardCalendar-like board showing all days in sprint.Focusing on deadlines and deliverables.Kanban board showing different stages in work pipeline. Focusing on DONE as quickly as possible.
Change of PlanCurrent sprint plan CANNOT be changed.New stories go to backlog for next sprint.New stories can be added to beat. Number of work-in-progress (WIP) items should be limited.
ProsMore predictable and reliable. Better scalability.Faster and more flexible.
ConsMore management overhead.Less flexibility for urgent works.Less predictability.Hard to scale.

Both Scrum and Kanban require:

The goal of planning is:

When sizing stories in Scrum,

Scrumban tries to bring the best of both worlds while making some compromisation on both sides. In Scrumban, stories are still sized and the key metric is still team velocity, but Scrumban can take in new stories into a sprint as far as another story with similar size is pushed out. So, the total number of stories planned for the sprint stays the same.