Scrumban

Definition

Scrumban is a hybrid work-management approach that blends Scrum and Kanban. It keeps some of Scrum’s coordination structure while adopting Kanban’s emphasis on pull-based flow, work visualization, and work-in-progress limits.

---

Core Ideas

Hybrid Structure

The source notes describe Scrumban as Scrum + Kanban:

• use a Kanban board for visualization
• keep daily Scrum-style coordination
• pull work rather than assigning it
• use strict WIP limits
• relax or reduce the need for rigid role structure

Two Common Modes

Continuous-flow Scrumban

• no fixed timeboxes
• work moves fluidly based on team capacity
• lead time and cycle time are primary metrics

Timeboxed Scrumban

• keeps sprint-like iterations
• uses planning, review, and retrospectives
• may still use flow metrics alongside burndown-style tracking

Why Teams Adopt It

The notes point to two common situations:

1. a Scrum team matures and wants more flow efficiency, so it evolves toward Kanban through Scrumban
2. a newer organization wants more structure than pure Kanban but cannot fully support formal Scrum roles

Feature Freeze and Triage

Scrumban can also support deadline-oriented triage. As a deadline approaches, the team can freeze lower-priority items and focus only on the most important unfinished work.

---

Benefits

• more flexible than pure Scrum
• more structured than pure Kanban for some teams
• helps teams transition between frameworks without a full reset
• supports pull-based flow while preserving useful coordination rituals

Trade-Offs

• can become vague if the team does not make its policies explicit
• may inherit the downsides of both Scrum and Kanban if adopted carelessly
• requires teams to be intentional about whether they are timeboxed or continuous-flow

---

Relationships

• Agile — Scrumban is an agile-compatible hybrid approach
• Scrum — Scrum contributes planning/review/retro structure
• Kanban — Kanban contributes flow, visualization, and WIP limits
• Agile and Team Processes — Scrumban is one of the bridge methods in the broader process landscape