← Back to blog

Scrumban: the best of both worlds

scrumban scrum kanban

Some teams find Scrum too rigid and Kanban too loose. For those cases, Scrumban offers a middle ground: the structure of Scrum with the flexibility of Kanban.

What is Scrumban?

Scrumban started as a transition from Scrum to Kanban, but has evolved into its own standalone model. It takes:

From Scrum:

  • Fixed-length sprints
  • Daily meetings
  • Retrospectives
  • Sprint goal

From Kanban:

  • WIP limits (work-in-progress limits)
  • Continuous flow within the sprint
  • No rigid scope commitment at the start of a sprint
  • Lead time as a metric

How it works in practice

On-demand planning

Instead of a big Sprint Planning at the beginning, planning happens when the backlog is running low. The team pulls the number of items needed to “fill” the board up to the WIP limits.

Flow-focused dailies

The daily standup continues, but instead of “yesterday/today,” the focus is: “What’s blocked? What’s close to completion? Does anyone need help keeping the flow moving?”

WIP limits by column

Example board:

  • To Do: no limit
  • In Progress: max 3 items per person
  • Code Review: max 5 items total
  • Testing: max 3 items
  • Done: no limit

When a column hits its limit, the team focuses on clearing it before pulling new work.

When to choose Scrumban

  • Maintenance team — Scrum sprints don’t make sense with unpredictable demand
  • Mature product team — already has discipline but needs more flexibility
  • Support + features — a team handling urgent bugs AND development
  • Gradual transition — a team wanting to move from Scrum to Kanban without a shock

Estimation in Scrumban

Scrumban doesn’t abandon estimation — it adapts it:

  • New items: Regular Planning Poker, since the team needs a baseline to prioritize
  • Recurring items (bugs): use historical lead time — “similar bugs took an average of 2 days”
  • Continuous refinement: estimate backlog items asynchronously, not just during planning meetings

Key metrics

  • Lead Time: time from “request” to “delivery”
  • Cycle Time: time from “work started” to “delivery”
  • Throughput: items delivered per week
  • Cumulative Flow Diagram: visualizes bottlenecks in the flow

Advantages over pure Scrum

  • Less ceremony overhead
  • Faster response to priority changes
  • Less pressure from “sprint commitments”
  • Focus on flow and eliminating bottlenecks

Advantages over pure Kanban

  • Maintains rhythm and discipline
  • Retrospectives ensure continuous improvement
  • Sprint goals provide direction
  • Less risk of becoming “just a ticket queue”

Conclusion

Scrumban is ideal for teams that already have agile maturity but feel Scrum is slowing down their flow. It’s not “Scrum lite” or “Kanban with meetings” — it’s an intentional approach that combines the best of both worlds.