Skip to content
BENIBIX Learn

Scrumban

Business📋 Agile DeliveryFrameworks

Also known as Scrum-ban

A mix of Scrum and Kanban. Keep some Scrum meetings and run the work on a Kanban board.

Think of it like

It is like a school day with set lessons and a lunch line. Some things run on the clock. Some run as they come.

Example

A support team keeps a retro every two weeks but drops sprints. When fewer than five cards wait in the ready column, they hold a short planning meeting.

Why it matters

Many teams find pure Scrum too stiff for work that arrives every day. Scrumban keeps the useful rhythm without the fixed sprint.

Definition

Scrumban is a mix of Scrum and Kanban. A team keeps some Scrum habits, like regular planning and retrospectives. It adds Kanban's board, its limits on work in progress and its pull. Planning often happens when the to-do column runs low, not on a fixed date. Corey Ladas gave it its name around 2008, as a path for Scrum teams moving toward Kanban.
Scrumban runs the work on a board like this one. Planning starts when the to-do column runs low.

Common mistake

Calling any team that dropped some Scrum rules Scrumban. Without limits and pull, it is just Scrum with gaps.

Key takeaways

  1. 1
    Keep the rhythm. Regular retros and reviews stay.
  2. 2
    Add the board. Work flows under WIP limits.
  3. 3
    Plan on demand. Refill when the queue runs low.

Compare

Learn it properly