Scrumban

Overview

Scrumban is a hybrid agile framework that merges the best elements of Scrum and Kanban, providing teams with the structure of Scrum's ceremonies and sprints while leveraging Kanban's visual management and continuous flow principles.

Origin and Purpose

Originally developed by teams transitioning from Scrum to Kanban, Scrumban emerged as a practical middle ground that addresses limitations in both methodologies. It's particularly effective for teams doing both planned work and responding to frequent urgent requests.

Key Elements from Scrum

Sprint Structure

• Time-boxed iterations (typically 1-2 weeks)
• Sprint planning to commit to work
• Sprint goals for focus and alignment

Ceremonies

• Sprint Planning: Plan work for the iteration
• Daily Standup: Brief daily sync (kept from Scrum)
• Sprint Review: Demonstrate completed work to stakeholders
• Retrospective: Reflect and improve processes

Roles (Optional)

• Product Owner: Manages backlog and priorities
• Scrum Master/Facilitator: Removes blockers and facilitates
• Development Team: Cross-functional executors

Key Elements from Kanban

Visual Management

• Kanban board showing all work in progress
• Columns representing workflow stages
• Cards showing individual tasks or stories

Work-in-Progress Limits

• Limit concurrent work to prevent overload
• Identify bottlenecks quickly
• Maintain sustainable pace

Continuous Flow

• Pull new work as capacity allows
• No strict sprint boundaries for urgent work
• Flexible work intake between planning sessions

Flow Metrics

• Cycle time: How long tasks take to complete
• Lead time: Time from request to delivery
• Throughput: Number of items completed per period

How Scrumban Works

Planning

1. Maintain prioritized backlog (from Scrum)
2. Plan work in sprint increments (from Scrum)
3. Pull new work when capacity available (from Kanban)
4. Set WIP limits for each workflow stage (from Kanban)

Execution

1. Team pulls highest priority work within WIP limits
2. Work flows through stages on Kanban board
3. Daily standup around the board
4. New urgent work can be pulled mid-sprint if WIP allows

Review and Adapt

1. Sprint review for stakeholder demo
2. Retrospective for process improvement
3. Analyze flow metrics for optimization
4. Adjust WIP limits and process as needed

Benefits of Scrumban

Flexibility

• Handle both planned sprints and urgent requests
• Adjust to changing priorities mid-sprint
• Scale ceremonies based on team needs

Visibility

• Kanban board shows real-time status
• Clear view of bottlenecks and blockers
• Easy stakeholder communication

Continuous Improvement

• Retrospectives drive process evolution
• Flow metrics reveal opportunities
• Iterative refinement of WIP limits

Reduced Waste

• WIP limits prevent overburdening
• Focus on completing work, not starting it
• Less time in planning meetings

When to Use Scrumban

Ideal For:

• Support teams with planned and unplanned work
• Teams transitioning from Scrum to Kanban (or vice versa)
• Maintenance teams with both projects and bug fixes
• Teams needing sprint structure but more flexibility
• Product teams with frequent priority changes

Not Ideal For:

• Teams new to agile (start with pure Scrum or Kanban)
• Highly predictable work (pure Kanban may be better)
• Teams requiring strict sprint commitments (use Scrum)

Implementation Tips

1. Start with Your Current Process: Add Kanban elements to Scrum or vice versa
2. Set Appropriate WIP Limits: Start conservative, adjust based on data
3. Keep Valuable Ceremonies: Drop ceremonies that don't add value
4. Visualize Everything: Make all work visible on the board
5. Measure and Adapt: Use metrics to guide improvements

Common Configurations

Scrum-Heavy Scrumban

• 2-week sprints with commitments
• All Scrum ceremonies maintained
• Kanban board for visualization
• Loose WIP limits

Kanban-Heavy Scrumban

• Continuous flow with periodic planning
• Strict WIP limits
• Lightweight ceremonies (standup, retro)
• Optional sprint structure

Balanced Scrumban

• 1-week sprints
• WIP limits enforced
• Core ceremonies (planning, standup, retro)
• Flexible work intake between planning

Scrumban vs. Pure Methodologies

vs. Scrum:

• More flexible work intake
• Focus on flow, not just sprint goals
• Lighter planning burden

vs. Kanban:

• More structure through sprints
• Regular cadence for planning and review
• Stronger team alignment through ceremonies