108 - Scrumban
Goal
Understand Scrumban as an evolutionary Agile approach that combines Scrum's structured planning with Kanban's flow optimization, enabling teams to improve delivery without abandoning existing Agile practices.
By the end of this chapter, readers should understand that Scrumban is not simply a hybrid framework but a continuous improvement approach that helps teams evolve their way of working based on evidence and flow.
Reading Time
| Level | Estimated Time |
|---|---|
| Quick Overview | 18 min |
| Complete Reading | 100–120 min |
| Including References | 130–150 min |
Mind Map
Scrumban
│
├── Scrum Foundations
│ ├── Planning
│ ├── Reviews
│ ├── Retrospectives
│ └── Product Backlog
│
├── Kanban Practices
│ ├── Pull
│ ├── WIP Limits
│ ├── Flow
│ ├── Metrics
│ └── Continuous Improvement
│
├── Continuous Evolution
│ ├── Policies
│ ├── Bottlenecks
│ ├── Adaptation
│ └── Optimization
│
├── Modern Engineering
│ ├── DevOps
│ ├── Platform Teams
│ ├── Product Teams
│ └── Service Teams
│
└── Learning
Table of Contents
1. Introduction
Many software teams begin their Agile journey with Scrum.
Scrum provides structure, clear roles, regular planning, and short feedback cycles that help teams learn how to deliver software iteratively.
As teams mature, however, new challenges often emerge.
Work arrives unexpectedly.
Production support interrupts Sprint commitments.
Priorities change more frequently than Sprint boundaries allow.
Some work items remain blocked while others accumulate, reducing overall delivery efficiency.
Rather than replacing Scrum entirely, many teams begin introducing Kanban practices to improve flow.
This gradual evolution gave rise to Scrumban.
Scrumban combines Scrum's planning and empirical learning with Kanban's flow-based optimization, allowing teams to evolve their process based on evidence rather than replacing one framework with another.
Today, many Agile teams unknowingly work in a Scrumban style by combining Sprint planning, Product Backlogs, Kanban boards, Work In Progress (WIP) limits, and flow metrics.
This chapter explores how Scrumban helps organizations continuously improve software delivery by evolving existing Agile practices instead of replacing them.
2. Why Scrumban Exists
🎯 Core Idea
Scrumban exists to help Scrum teams improve flow without abandoning the practices that already work well.
Scrum provides an excellent starting point for teams learning Agile.
However, as products, organizations, and delivery systems become more complex, teams often discover that additional flow-based practices improve responsiveness and delivery performance.
Scrumban embraces continuous evolution rather than wholesale replacement.
2.1 When Scrum Isn't Enough
Scrum works particularly well when work can be planned into relatively stable Sprint Goals.
In practice, many teams experience additional demands such as:
- Unplanned production incidents.
- Operational support requests.
- Urgent business priorities.
- Cross-team dependencies.
- Interrupt-driven work.
Attempting to force all work into fixed Sprint commitments can reduce flexibility and increase frustration.
Scrumban introduces flow-based practices that help teams respond to changing demand while preserving Scrum's strengths.
🌊 Flow Insight
A framework should adapt to the work—not force the work to adapt to the framework.
2.2 Origins of Scrumban
Scrumban was introduced by Corey Ladas as an evolutionary approach for Scrum teams seeking greater flexibility.
Rather than creating a completely new framework, Ladas proposed combining Scrum's empirical planning with Kanban's focus on flow.
The objective was not to replace Scrum.
Instead, teams would gradually introduce Kanban practices as their needs evolved.
This philosophy remains one of Scrumban's defining characteristics.
2.3 Evolution Instead of Replacement
One of Scrumban's most important ideas is that improvement should be evolutionary.
Teams begin with an existing process.
They measure how work flows.
They identify bottlenecks.
They introduce targeted improvements.
They repeat the cycle.
This approach avoids unnecessary disruption while encouraging continuous learning.
Rather than asking teams to adopt an entirely new methodology, Scrumban helps them improve the one they already have.
🔗 How These Concepts Work Together
Scrum provides structure.
Kanban improves flow.
Measurement identifies bottlenecks.
Incremental improvements optimize delivery.
Together, these ideas create a continuously evolving Agile delivery system.
🌊 Flow Insight
Continuous improvement is usually achieved through many small changes rather than one large transformation.
3. The Scrumban Philosophy
🎯 Core Idea
Scrumban encourages teams to continuously improve their way of working by combining structured planning with flow-based optimization.
Rather than defining a fixed methodology, Scrumban provides principles that help teams evolve based on evidence and operational experience.
Keep What Works
Scrumban does not require teams to abandon Scrum.
If Sprint Planning, Sprint Reviews, or Retrospectives provide value, they remain.
The objective is continuous improvement rather than methodological purity.
Teams should preserve practices that contribute to successful delivery while adapting those that no longer meet their needs.
Improve Flow
Flow represents the movement of work from idea to customer value.
Improving flow involves:
- Reducing waiting.
- Eliminating bottlenecks.
- Limiting unfinished work.
- Delivering smaller increments.
- Accelerating feedback.
Smooth flow generally produces more predictable delivery than increasing individual utilization.
Pull Instead of Push
Traditional planning often assigns work to individuals regardless of current capacity.
Scrumban encourages a pull system, where team members pull new work only when capacity becomes available.
This approach:
- Reduces multitasking.
- Limits Work In Progress.
- Improves focus.
- Reduces context switching.
- Increases delivery stability.
Continuous Prioritization
Rather than reviewing priorities only at Sprint boundaries, Scrumban encourages continuous backlog refinement.
Business priorities evolve continuously.
The delivery system should evolve alongside them.
Continuous prioritization enables organizations to respond more quickly to changing customer needs while maintaining delivery flow.
Evolutionary Change
Perhaps the defining characteristic of Scrumban is its commitment to incremental improvement.
Rather than redesigning the delivery process, teams continuously inspect:
- Flow metrics.
- Bottlenecks.
- Waiting time.
- Delivery predictability.
- Customer feedback.
Each improvement builds upon previous learning.
🔗 How These Concepts Work Together
Successful Scrum practices remain.
Flow improvements reduce delays.
Pull systems improve focus.
Continuous prioritization improves responsiveness.
Evolutionary change strengthens delivery over time.
Together, these ideas enable Agile teams to improve continuously without unnecessary disruption.
🌊 Flow Insight
Improving the system usually creates greater benefits than asking individuals to work harder.
4. Core Scrumban Practices
🎯 Core Idea
Scrumban combines selected Scrum practices with Kanban techniques to create a continuously improving delivery system.
The objective is not to maximize process, but to improve flow while preserving valuable Agile practices.
Scrum Events
Many Scrumban teams continue using Scrum events, including:
- Sprint Planning.
- Daily Scrum.
- Sprint Review.
- Sprint Retrospective.
Teams may adapt the frequency or format of these events according to their operational needs.
The emphasis remains on supporting learning rather than enforcing ceremony.
Kanban Board
The Kanban board provides visibility into the current state of work.
Typical workflow stages include:
- Ready.
- In Progress.
- Review.
- Testing.
- Done.
Visualizing work enables teams to identify bottlenecks and improve flow.
WIP Limits
Work In Progress (WIP) limits restrict the number of items simultaneously under development.
Benefits include:
- Improved focus.
- Reduced context switching.
- Faster completion.
- Better flow.
- Earlier feedback.
Limiting WIP encourages teams to finish work before starting additional tasks.
Pull System
Rather than assigning work centrally, team members pull new work when capacity becomes available.
Pull systems improve delivery by:
- Balancing workload.
- Reducing waiting.
- Increasing ownership.
- Supporting continuous flow.
Work enters development only when the system is ready.
Flow Metrics
Scrumban encourages teams to measure system performance objectively.
Common metrics include:
- Lead Time.
- Cycle Time.
- Throughput.
- Work In Progress.
- Flow Efficiency.
These metrics reveal opportunities for continuous improvement.
🔗 How These Concepts Work Together
Scrum events encourage learning.
Kanban boards improve visibility.
WIP limits stabilize flow.
Pull systems balance workload.
Flow metrics guide improvement.
Together, these practices create a delivery system that continuously adapts to changing organizational needs.
5. Scrumban in Modern Software Engineering
🎯 Core Idea
Scrumban reflects how many modern engineering teams actually work today.
Although relatively few organizations formally identify themselves as practicing Scrumban, its principles are widely adopted across modern software engineering.
Its emphasis on continuous evolution aligns naturally with contemporary delivery practices.
Product Teams
Product Teams frequently combine Sprint planning with continuous backlog refinement and flow-based delivery.
This enables structured planning while maintaining responsiveness to changing customer priorities.
Platform Engineering
Platform Teams often receive unpredictable requests from multiple engineering teams.
Flow-based work management, WIP limits, and pull systems help them balance planned improvements with operational support.
Scrumban provides greater flexibility than fixed Sprint commitments in these environments.
DevOps
DevOps emphasizes continuous delivery, automation, rapid feedback, and system optimization.
Scrumban complements these practices by improving flow across the software delivery lifecycle.
Rather than optimizing individual phases, teams continuously optimize the entire delivery system.
Service Delivery
Support, operations, infrastructure, and internal service teams frequently manage interrupt-driven work.
Scrumban enables these teams to combine prioritization with continuous flow while maintaining visibility and predictability.
Continuous Improvement
Perhaps Scrumban's greatest contribution is its emphasis on continuous process evolution.
Teams regularly examine:
- Delivery metrics.
- Customer feedback.
- Workflow bottlenecks.
- Organizational constraints.
- Team collaboration.
Improvements are introduced incrementally rather than through large organizational transformations.
Comparison
| Modern Practice | Scrumban Contribution |
|---|---|
| Product Teams | Continuous planning with flow optimization |
| Platform Engineering | Managing planned and unplanned work |
| DevOps | End-to-end flow improvement |
| Service Delivery | Flexible handling of interrupt-driven work |
| Continuous Improvement | Evolutionary process adaptation |
🔗 How These Concepts Work Together
Scrum provides structure.
Kanban improves flow.
Continuous measurement guides improvement.
Modern engineering teams adapt their processes as their products and organizations evolve.
Together, these ideas demonstrate that Scrumban is less a distinct framework than an evolutionary approach to building more effective Agile delivery systems.
🏛️ Architecture Insight
Stable architectures enable stable flow.
Modular systems, loosely coupled services, trunk-based development, automated testing, and continuous integration reduce dependencies and bottlenecks, allowing teams to deliver work continuously without being constrained by architectural complexity.
6. Measuring Success
🎯 Core Idea
Scrumban measures success by improving the flow of value through the delivery system rather than maximizing individual productivity or process compliance.
Unlike traditional project metrics, Scrumban focuses on how efficiently work moves from idea to customer value.
By measuring flow objectively, teams can identify bottlenecks, reduce delays, and continuously improve their delivery process.
Flow Efficiency
Flow Efficiency measures the proportion of time work spends actively being developed compared to the total time it spends in the system.
For example:
10 Days Total
│
├── 2 Days Active Work
└── 8 Days Waiting
Flow Efficiency = 20%
Low Flow Efficiency often indicates:
- Waiting for reviews.
- Approval delays.
- Dependencies.
- Context switching.
- Bottlenecks.
Improving Flow Efficiency usually has a greater impact than increasing individual productivity.
🌊 Flow Insight
Most delays occur while work is waiting—not while people are working.
Cycle Time
Cycle Time measures how long it takes to complete work after implementation begins.
Monitoring Cycle Time helps teams:
- Detect bottlenecks.
- Improve predictability.
- Reduce unnecessary delays.
- Increase delivery confidence.
Smaller and more consistent Cycle Times generally indicate healthier delivery systems.
Lead Time
Lead Time measures the total elapsed time from customer request to delivered value.
It represents the customer's perspective.
Reducing Lead Time allows organizations to:
- Respond faster.
- Learn sooner.
- Reduce business risk.
- Increase customer satisfaction.
Many Scrumban improvements ultimately aim to shorten Lead Time.
Delivery Predictability
Predictable delivery allows organizations to make better business decisions.
Rather than relying on optimistic estimates, Scrumban encourages teams to forecast delivery using historical flow data.
Stable flow generally produces more reliable forecasts than detailed upfront planning.
Continuous Improvement
Perhaps the most important measure of success is whether the delivery system improves over time.
Teams regularly evaluate:
- Flow Metrics.
- Delivery quality.
- Customer feedback.
- Bottlenecks.
- Team collaboration.
Every improvement strengthens the overall delivery system.
🔗 How These Concepts Work Together
Flow Efficiency identifies waste.
Cycle Time measures execution.
Lead Time reflects customer experience.
Predictable Delivery improves planning.
Continuous Improvement strengthens the system.
Together, these metrics help teams continuously optimize the flow of customer value.
🌊 Flow Insight
Optimizing flow creates more value than maximizing utilization.
7. Bringing Scrumban Together
🎯 Core Idea
Scrumban is less a framework than a mindset of continuous process evolution.
Rather than asking teams to replace Scrum or Kanban, Scrumban encourages them to evolve their delivery process based on evidence, feedback, and changing organizational needs.
Its greatest strength lies in helping teams improve gradually instead of pursuing disruptive process transformations.
7.1 Evolution over Revolution
Large process changes often introduce unnecessary disruption.
Scrumban promotes small, incremental improvements.
Teams observe their current workflow.
They identify constraints.
They introduce one improvement.
They measure the outcome.
They repeat.
This evolutionary approach reduces risk while supporting continuous organizational learning.
7.2 Scrumban and Modern Agile
Many modern Agile teams unknowingly apply Scrumban principles.
Examples include:
- Scrum planning with Kanban boards.
- WIP limits within Sprint workflows.
- Continuous Backlog Refinement.
- Flow Metrics.
- Pull-based work allocation.
Rather than following a single methodology, teams continuously adapt their delivery practices.
This reflects Scrumban's central philosophy.
7.3 Flow-Driven Organizations
Organizations increasingly optimize the entire value stream rather than individual teams.
Flow-driven organizations emphasize:
- Fast customer feedback.
- Reduced bottlenecks.
- Cross-functional collaboration.
- Continuous delivery.
- Evidence-based improvement.
Success depends less on following a prescribed framework and more on improving the system through which value is delivered.
🔗 How These Concepts Work Together
Continuous measurement reveals opportunities.
Small improvements optimize flow.
Improved flow accelerates learning.
Learning strengthens delivery.
Delivery creates customer value.
Together, these principles demonstrate that Scrumban is fundamentally an approach to continuous organizational evolution.
🏛️ Architecture Insight
Delivery flow depends on architectural flow.
Modular architectures, loosely coupled services, trunk-based development, automated testing, and deployment pipelines reduce dependencies and enable teams to deliver continuously without unnecessary coordination overhead.
8. Common Misconceptions
Scrumban is frequently misunderstood because it combines ideas from both Scrum and Kanban.
The following misconceptions are among the most common.
Scrumban is simply Scrum plus Kanban
Scrumban is not a checklist of Scrum ceremonies combined with a Kanban board.
It is an evolutionary approach that continuously adapts processes based on evidence.
Teams must abandon Scrum
Most Scrumban teams continue using many Scrum practices.
Planning, Reviews, and Retrospectives often remain valuable.
Only practices that no longer support effective delivery are adapted.
Scrumban eliminates planning
Planning remains essential.
The difference is that planning becomes more continuous and evidence-driven rather than occurring exclusively at Sprint boundaries.
WIP limits reduce productivity
Limiting Work In Progress improves focus and reduces context switching.
Completing work more consistently generally produces higher throughput than starting more work simultaneously.
Flow Metrics replace customer value
Flow Metrics help improve delivery.
Customer value remains the ultimate objective.
Improving flow without delivering meaningful outcomes provides little benefit.
Scrumban is only suitable for support teams
Although frequently adopted by Platform, Infrastructure, and Service Teams, Scrumban also works effectively for Product Teams seeking greater delivery flexibility.
9. 💼 In Practice
Case Study: Evolving Scrum into Scrumban
A Product Team used Scrum successfully for several years.
As the product matured, however, the team increasingly handled:
- Production incidents.
- Customer support requests.
- Small enhancements.
- Regulatory changes.
Sprint commitments became difficult to maintain because urgent work frequently interrupted planned development.
Step 1 — Visualize Flow
The team expanded its Scrum board into a Kanban-style workflow.
Additional workflow stages improved visibility into waiting, reviews, and testing.
Step 2 — Introduce WIP Limits
Rather than starting multiple items simultaneously, the team limited Work In Progress.
Developers focused on completing existing work before beginning new tasks.
Delivery became smoother and bottlenecks became immediately visible.
Step 3 — Measure Flow
The team began monitoring:
- Lead Time.
- Cycle Time.
- Throughput.
- Flow Efficiency.
These metrics guided future improvements.
Step 4 — Evolve Continuously
Sprint Planning and Sprint Reviews remained.
However, backlog refinement became continuous and urgent work entered the system through explicit pull policies.
The team evolved naturally without replacing Scrum.
Results
The organization achieved:
- Shorter Lead Time.
- More predictable delivery.
- Improved responsiveness.
- Reduced multitasking.
- Better customer satisfaction.
Lessons Learned
The team concluded that:
- Scrum provided valuable structure.
- Kanban improved flow.
- Continuous measurement improved decision-making.
- Small process changes produced significant long-term benefits.
- Evolution proved more effective than wholesale process replacement.
Remember
Scrumban does not ask teams to choose between Scrum and Kanban.
It encourages them to continuously improve the way they deliver value.
10. 💡 Did You Know?
Scrumban was introduced by Corey Ladas
Corey Ladas proposed Scrumban as an evolutionary path for Scrum teams seeking greater flexibility through Kanban practices.
Many teams practice Scrumban without realizing it
Organizations often begin with Scrum and gradually introduce Kanban practices such as WIP limits, pull systems, and Flow Metrics.
Over time, they naturally evolve toward Scrumban.
Flow Metrics are becoming increasingly important
Modern engineering organizations increasingly rely on Lead Time, Cycle Time, Throughput, and Flow Efficiency to understand delivery performance instead of focusing solely on Velocity.
Scrumban aligns naturally with DevOps
Continuous flow, automation, rapid feedback, and incremental improvement closely complement DevOps and Continuous Delivery practices.
Evolutionary change reduces organizational resistance
Small, evidence-based improvements are generally easier to adopt and sustain than large-scale process transformations.
Scrumban supports many different team types
Product Teams, Platform Teams, DevOps Teams, Infrastructure Teams, Internal Service Teams, and Support Teams can all benefit from Scrumban principles while adapting practices to their own context.
11. 📝 Key Takeaways
After completing this chapter, you should understand that:
- Scrumban combines Scrum's planning with Kanban's flow optimization.
- It is best understood as an evolutionary approach rather than a standalone framework.
- Teams should preserve practices that create value while improving those that do not.
- Pull systems and WIP limits improve delivery stability and focus.
- Flow Metrics provide objective insight into system performance.
- Continuous prioritization improves responsiveness to changing business needs.
- Small, incremental improvements are generally more effective than large process transformations.
- Modern Product, Platform, DevOps, and Service Teams frequently apply Scrumban principles.
- Improving flow increases organizational adaptability.
- Continuous evolution is the defining characteristic of Scrumban.
Remember
Scrum teaches teams how to learn.
Kanban teaches teams how work flows.
Scrumban teaches teams how to continuously improve both.
12. 📚 Further Reading
Continue With
The final framework chapter explores Agile at organizational scale:
- 109 - Scaled Agile Framework (SAFe)
- 110 - Agile Estimation & Forecasting
Related Topics
Scrumban
- Scrumban: Essays on Kanban Systems for Lean Software Development — Corey Ladas
Kanban
- Kanban — David J. Anderson
- Actionable Agile Metrics for Predictability — Daniel S. Vacanti
Scrum
- Scrum Guide — Ken Schwaber & Jeff Sutherland
- Agile Software Development with Scrum — Ken Schwaber & Mike Beedle
Lean & Flow
- The Principles of Product Development Flow — Donald G. Reinertsen
- Lean Software Development — Mary & Tom Poppendieck
Modern Engineering
- Accelerate — Nicole Forsgren, Jez Humble & Gene Kim
- The DevOps Handbook — Gene Kim et al.
- Team Topologies — Matthew Skelton & Manuel Pais
Looking Ahead
As organizations grow, coordinating multiple Agile teams introduces new challenges that individual team-level frameworks do not fully address.
The next chapter explores the Scaled Agile Framework (SAFe), examining how large organizations attempt to align strategy, governance, portfolio management, and software delivery across many teams. It also discusses both the strengths and the most common criticisms of SAFe, helping readers understand when scaling frameworks may—or may not—be appropriate.
Next Chapter
109 - Scaled Agile Framework (SAFe)
Explore how SAFe extends Agile principles to large organizations, balancing strategic alignment, portfolio management, architectural coordination, and continuous delivery across multiple teams while understanding the trade-offs involved in scaling Agile.