Scrum vs Kanban: should you choose one, or can you combine them?

Scrum is a framework structured around Sprints, with defined roles, events, and artifacts. Kanban, originally derived from the Toyota Production System, is a workflow management method centered on visualization, limiting work in process (WIP), and continuously improving flow.

Contrary to a common belief, these two approaches are not mutually exclusive. Many Scrum teams incorporate Kanban practices to visualize their Sprint Backlog, limit their work in process, and measure flow metrics such as lead time or cycle time.

Scrum.org formalized this combination under the name Scrum with Kanban: an approach that applies Kanban practices — flow visualization, work-in-process limits, queue management — within the Scrum framework itself, without replacing its roles or events.

The goal is not to turn Scrum into Kanban, but to use flow data to make better decisions during Sprint Planning, the Daily Scrum, or the Sprint Retrospective, relying on facts rather than impressions.

Limiting work in process reduces multitasking and context switching, which often speeds up the delivery of Sprint Backlog items. Visualizing flow through a Kanban board immediately surfaces bottlenecks, for example when several items pile up waiting for code review.

Flow metrics, such as average cycle time, also help better forecast the team's capacity for future Sprints, as a complement to — not a replacement for — traditional point-based estimation.

The Professional Scrum with Kanban™ I (PSK I) certification validates your ability to combine Scrum and Kanban coherently: understanding flow metrics, applying meaningful work-in-process limits, and using this data to continuously improve team performance.

This certification is particularly relevant for Scrum Masters working in contexts where delivery predictability is a major concern, or for teams managing a continuous stream of requests alongside their Sprints.