Scrumban
What is Scrumban?
Scrumban is a hybrid of Scrum and Kanban in which teams keep some Scrum events, such as retrospectives and reviews, but run daily work on a Kanban board with WIP limits and pull-based flow. Corey Ladas popularized the term.
Updated November 2026 · 3 min read
Scrumban is a hybrid agile approach that combines parts of Scrum with the flow-based practices of Kanban. A Scrumban team typically keeps some Scrum structure, such as regular planning, reviews and retrospectives, while managing day-to-day work on a Kanban board with work-in-progress (WIP) limits and a pull system. Planning happens when the queue of ready work runs low rather than only at fixed sprint boundaries.
The term was popularized by Corey Ladas, whose 2008 essay and 2009 book Scrumban: Essays on Kanban Systems for Lean Software Development described it as a way for Scrum teams to move gradually toward Kanban's lean, flow-based practices. Today the word is used more loosely for almost any mix of the two, which is why teams should spell out which practices they actually use.
What Scrumban takes from Scrum and Kanban
| From Scrum | From Kanban |
|---|---|
| Regular retrospectives and reviews | A visual board showing the whole workflow |
| A prioritized backlog | WIP limits on each stage |
| Often a daily standup | Pull-based work: start new items only when capacity frees up |
| Sometimes a fixed iteration for reviews and planning | Flow metrics such as cycle time and throughput |
| Cross-functional teams | Explicit policies for each column |
Scrumban usually drops or relaxes the sprint commitment, formal story-point estimation and, in some teams, the separate Scrum roles.
How Scrumban planning works
- On-demand planning. The team sets a trigger, such as "plan when fewer than four items are in the Ready column," and plans only then.
- Bucket-size planning. Ladas described holding ideas in progressively more detailed buckets, for example one-year, six-month and three-month horizons, with items moving closer as they become likely to be built.
- Feature freeze and triage. Before a release date, the team stops starting new features and decides which in-progress items can finish in time.
How to implement Scrumban
- Map the current workflow. Put every real stage on the board, including review and testing, not an idealized process.
- Set WIP limits. Start near the current level of WIP and lower it gradually to expose bottlenecks.
- Define a Ready column and planning trigger. Decide how many items should be ready and when to refill.
- Keep the improvement events. Hold retrospectives on a regular cadence; they are the engine of improvement.
- Measure flow. Track cycle time and throughput instead of, or as well as, velocity.
A hypothetical example
Consider a hypothetical product team that maintains a customer-facing app and handles frequent urgent requests from support. In two-week sprints, a third of planned work is regularly displaced by interruptions, and the sprint commitment has stopped meaning anything. The team switches to Scrumban: it keeps a weekly review and a retrospective every two weeks, removes the sprint commitment, and sets WIP limits.
Before the change, the team averaged 12 items in progress and finished 4 items a week. By Little's Law, average cycle time equals WIP divided by throughput, so items took about 12 ÷ 4 = 3 weeks from start to finish. After lowering total WIP to 8 while throughput holds at 4 items a week, average cycle time falls to about 8 ÷ 4 = 2 weeks. Urgent requests now go to the top of the Ready column and are pulled as soon as someone finishes an item, without breaking a sprint plan.
Common pitfalls
- Scrumban as an excuse. Dropping the hard parts of Scrum, such as retrospectives, without adopting Kanban's discipline leaves a team with neither.
- No real WIP limits. Limits that are routinely ignored, or set so high they never bind, do not change flow.
- Unclear definitions. Because Scrumban is loosely defined, two teams using the name may work very differently. Write down your rules.
- Losing forecasting. Without sprints, teams need throughput data to answer "when will it be done?"
Scrumban sits between Scrum and Kanban; the trade-offs are covered in more depth under Kanban vs. Scrum. A tool-oriented variant of the same idea is Kanplan.
Frequently asked questions
How is Scrumban different from Scrum?
Scrumban keeps parts of Scrum, such as retrospectives, reviews and a prioritized backlog, but usually drops or relaxes the sprint commitment and formal story-point estimation. Daily work runs on a Kanban board with WIP limits and pull-based flow, and planning happens when the ready queue runs low instead of only at fixed sprint boundaries.
How does planning work in Scrumban?
Scrumban teams plan on demand. They set a trigger, such as planning whenever fewer than four items sit in the Ready column, and refill only then. Corey Ladas also described bucket-size planning, holding ideas in one-year, six-month and three-month horizons, and a feature freeze with triage before a release date.
When should a team switch to Scrumban?
Scrumban suits teams whose sprint plans keep getting disrupted, such as product teams handling frequent urgent requests from support. If a large share of planned work is regularly displaced and the sprint commitment has stopped meaning anything, WIP limits and pull-based flow let urgent items go to the top of the Ready column without breaking a plan.
Related terms
Cycle Time
How long an item takes from the moment work starts until it is done.
Scrum
An agile framework of short Sprints, three roles and regular inspection.
Kanban
Visualizing work, limiting work in progress and improving the flow.
Kanban vs Scrum
Fixed Sprints with set roles versus continuous flow with WIP limits.