102 - Kanban

Goal

Understand Kanban as a Lean method for improving the flow of work through visualization, limiting Work In Progress (WIP), and continuous evolutionary change.

By the end of this chapter, readers should understand that Kanban is not simply a board with columns, but a management method designed to optimize value delivery by making work visible, managing flow, reducing bottlenecks, and continuously improving the system.

Rather than prescribing roles, ceremonies, or iterations, Kanban enables teams to evolve their existing way of working through incremental, evidence-based improvements.

Reading Time

Mind Map

Kanban
│
├── Foundations
│   ├── Lean Thinking
│   ├── Flow
│   ├── Pull System
│   └── Evolutionary Change
│
├── Core Practices
│   ├── Visualize Work
│   ├── Limit WIP
│   ├── Manage Flow
│   ├── Explicit Policies
│   ├── Feedback Loops
│   └── Continuous Improvement
│
├── Metrics
│   ├── Lead Time
│   ├── Cycle Time
│   ├── Throughput
│   ├── WIP
│   └── Flow Efficiency
│
├── Kanban in Software Engineering
│   ├── Product Development
│   ├── DevOps
│   ├── Platform Engineering
│   ├── SRE
│   └── Support Teams
│
├── Scaling Flow
│   ├── Portfolio Kanban
│   ├── Team Kanban
│   ├── Service Delivery
│   └── Value Streams
│
└── Continuous Improvement
    ├── Bottlenecks
    ├── Constraints
    ├── Kaizen
    └── Learning

Table of Contents

1. Introduction

2. Why Kanban Exists

   • 2.1 Flow over Utilization
   • 2.2 Origins in Lean Manufacturing
   • 2.3 Evolutionary Change

3. Kanban Principles

   • Start with What You Do Now
   • Agree to Pursue Incremental Change
   • Respect Current Roles and Responsibilities
   • Encourage Leadership at Every Level

4. Core Kanban Practices

   • Visualize Work
   • Limit Work In Progress (WIP)
   • Manage Flow
   • Make Policies Explicit
   • Implement Feedback Loops
   • Improve Collaboratively

5. Flow Metrics

   • Lead Time
   • Cycle Time
   • Throughput
   • Work In Progress
   • Flow Efficiency

6. Kanban in Modern Software Engineering

   • DevOps
   • Platform Engineering
   • Site Reliability Engineering
   • Product Development
   • Service Teams

7. Bringing Kanban Together

   • 7.1 Optimizing Flow
   • 7.2 Kanban and Scrum
   • 7.3 Continuous Evolution

8. Common Misconceptions

9. 💼 In Practice

10. 💡 Did You Know?

11. 📝 Key Takeaways

12. 📚 Further Reading

1. Introduction

Kanban is one of the simplest—and most misunderstood—methods in modern software engineering.

Many people associate Kanban with a board divided into columns such as To Do, In Progress, and Done.

While visualization is an important part of Kanban, the board itself is only a tool.

Kanban is fundamentally a method for improving the flow of work.

Its purpose is not to prescribe roles, ceremonies, or iterations.

Instead, Kanban helps organizations understand how work moves through a system, identify bottlenecks, reduce delays, and continuously improve the delivery of value.

Unlike Scrum, Kanban does not require organizations to redesign the way they work.

Instead, it encourages evolutionary change.

Teams begin with their existing process, make work visible, measure flow, and improve the system incrementally through evidence rather than assumptions.

This makes Kanban highly adaptable across software engineering, operations, product management, customer support, platform engineering, and many other knowledge work environments.

This chapter explores why flow matters, how Kanban improves it, and how modern software organizations use Kanban to deliver value more predictably and efficiently.

2. Why Kanban Exists

🎯 Core Idea

The objective is not to keep everyone busy.

The objective is to keep value flowing.

Organizations often attempt to improve productivity by increasing individual utilization.

However, Lean Thinking demonstrated that maximizing the utilization of every person frequently reduces the performance of the overall system.

Kanban was created to solve this problem.

Rather than optimizing individual activity, Kanban optimizes the movement of work through the entire value stream.

2.1 Flow over Utilization

Traditional organizations often measure success by asking questions such as:

• Is everyone busy?
• Are all teams fully utilized?
• Is every resource assigned work?

Kanban asks a different question:

How quickly does value reach the customer?

📦 Kanban Insight

High utilization often reduces flow.

When every individual is continuously busy:

• Work queues grow.
• Context switching increases.
• Waiting times become longer.
• Bottlenecks become harder to identify.
• Delivery slows.

Paradoxically, allowing spare capacity often improves the overall speed of delivery.

High Utilization
        │
        ▼
Long Queues
        │
        ▼
Long Wait Times
        │
        ▼
Slower Delivery

Optimized Flow
        │
        ▼
Smaller Queues
        │
        ▼
Faster Delivery

Kanban therefore measures success through the flow of value rather than the utilization of resources.

2.2 Origins in Lean Manufacturing

Kanban originated within the Toyota Production System.

The Japanese word Kanban (看板) literally means visual signal or signboard.

Toyota used Kanban cards to communicate demand between production stages.

Rather than producing inventory in advance, each stage produced work only when the next stage required it.

This became known as a Pull System.

The objective was to reduce:

• Inventory
• Waiting
• Waste
• Overproduction

Modern software engineering adopted these same ideas.

Although software is not manufactured physically, unfinished work behaves similarly to inventory.

The more unfinished work exists, the more delays, uncertainty, and coordination overhead accumulate.

Kanban therefore applies Lean principles to knowledge work.

2.3 Evolutionary Change

Unlike many frameworks, Kanban does not require organizations to redesign their processes before improvement can begin.

Instead, Kanban starts with the current system.

Teams observe how work flows today.

They identify constraints.

They introduce small improvements.

They measure the results.

Improvement becomes continuous rather than transformational.

Current Process
        │
        ▼
Visualize
        │
        ▼
Measure
        │
        ▼
Improve
        │
        ▼
Repeat

This evolutionary approach reduces resistance to change while encouraging continuous learning.

🔗 How These Concepts Work Together

Flow focuses attention on value rather than activity.

Lean Thinking explains why excessive work slows delivery.

Evolutionary change enables organizations to improve continuously without disrupting existing systems.

Together, these ideas form the foundation of Kanban.

📦 Kanban Insight

Kanban does not ask organizations to work differently tomorrow.

It asks them to improve slightly every day.

3. Kanban Principles

🎯 Core Idea

Kanban improves systems through evolutionary change rather than disruptive transformation.

Kanban defines four foundational principles that guide organizational improvement.

Rather than prescribing a new process, these principles help organizations improve the one they already have.

Start with What You Do Now

Kanban assumes that the current process contains valuable knowledge.

Teams do not need to redesign everything before improvement begins.

Instead, they first understand how work actually flows.

Improvement begins with observation rather than replacement.

Agree to Pursue Incremental Change

Large organizational transformations often create resistance.

Kanban encourages small, continuous improvements.

Each change is:

• Observable
• Measurable
• Reversible
• Easier to adopt

Small improvements accumulate into significant long-term change.

Respect Current Roles and Responsibilities

Kanban does not redefine organizational structures.

Existing responsibilities remain in place while the system evolves.

Respecting current roles reduces disruption and encourages collaboration during change.

Encourage Leadership at Every Level

Improvement is everyone's responsibility.

Leadership is not limited to managers.

Engineers.

Designers.

Product Managers.

Operations.

Support.

Every individual can identify opportunities to improve flow.

Continuous improvement therefore becomes a shared responsibility.

🔗 How These Concepts Work Together

Kanban begins with the existing system.

Improvement occurs through small changes.

Respect creates trust.

Leadership emerges throughout the organization.

Together, these principles enable sustainable organizational evolution.

4. Core Kanban Practices

🎯 Core Idea

Flow improves when work becomes visible, measurable, and actively managed.

Kanban defines six core practices that enable continuous improvement.

Visualize Work

Invisible work cannot be improved.

Kanban Boards make work visible.

Typical workflow:

Backlog
    │
    ▼
Ready
    │
    ▼
In Progress
    │
    ▼
Review
    │
    ▼
Testing
    │
    ▼
Done

Visualization exposes:

• Queues
• Blockers
• Bottlenecks
• Waiting
• Work distribution

Limit Work In Progress (WIP)

Limiting Work In Progress is one of Kanban's most important practices.

Rather than starting additional work, teams finish existing work first.

Benefits include:

• Faster delivery
• Less context switching
• Smaller queues
• Better quality
• Improved focus

Manage Flow

Managing flow means observing how work moves through the system.

Questions include:

• Where does work wait?
• Which stages become bottlenecks?
• Where is demand exceeding capacity?
• How can flow improve?

Flow becomes a measurable property of the system.

Make Policies Explicit

Teams improve more effectively when everyone understands how work moves.

Examples include:

• Definition of Ready
• WIP limits
• Pull policies
• Prioritization rules
• Service classes

Explicit policies reduce ambiguity and improve collaboration.

Implement Feedback Loops

Kanban encourages regular opportunities to inspect flow.

Examples include:

• Replenishment Meetings
• Delivery Reviews
• Flow Reviews
• Operations Reviews
• Retrospectives

Short feedback loops support continuous improvement.

Improve Collaboratively

Improvement should be evidence-based.

Teams use metrics, observations, and experimentation to evolve their process continuously.

Continuous improvement becomes an integral part of everyday work.

🔗 How These Concepts Work Together

Visualization exposes reality.

WIP limits reduce queues.

Managing flow identifies constraints.

Explicit policies improve consistency.

Feedback enables learning.

Collaboration sustains continuous improvement.

📦 Kanban Insight

Work waiting in a queue creates no customer value.

5. Flow Metrics

🎯 Core Idea

You cannot improve flow without understanding how work actually moves through the system.

Kanban uses flow metrics to reveal delays, bottlenecks, and opportunities for improvement.

The purpose of these metrics is not to evaluate individual performance.

It is to improve the performance of the system.

Why Measure Flow?

Without measurement, improvement becomes guesswork.

Flow metrics help teams answer questions such as:

• How long does work take?
• Where does work wait?
• How much work is completed?
• Where are bottlenecks emerging?

These insights guide evidence-based improvements.

Lead Time

Lead Time measures the total time from a customer's request until the work is delivered.

It represents the customer's experience.

Cycle Time

Cycle Time measures the time from when work begins until it is completed.

Unlike Lead Time, it excludes the time spent waiting before work starts.

Throughput

Throughput measures how many work items are completed during a given period.

It helps teams understand delivery capacity without estimating effort.

Work In Progress (WIP)

WIP measures how many items are currently being worked on.

High WIP usually leads to:

• Longer Lead Times
• More context switching
• Greater variability
• Increased delivery risk

Flow Efficiency

Flow Efficiency compares active work time with total elapsed time.

Flow Efficiency =
Active Work Time
────────────────────────
Total Lead Time

Many organizations discover that work spends far more time waiting than actively being developed.

Improving flow often means reducing waiting rather than increasing development speed.

🔗 How These Concepts Work Together

Lead Time reflects customer experience.

Cycle Time measures execution speed.

Throughput shows delivery capacity.

WIP exposes system load.

Flow Efficiency reveals waste.

Together, these metrics provide a comprehensive understanding of system flow.

6. Kanban in Modern Software Engineering

🎯 Core Idea

Kanban is not limited to software development.

It improves the flow of work wherever knowledge work exists.

Modern engineering organizations apply Kanban across many disciplines.

DevOps

Kanban improves the flow of changes from development to production.

Visualizing deployment pipelines and limiting WIP reduces deployment bottlenecks and accelerates feedback.

Platform Engineering

Platform teams frequently manage incoming requests, infrastructure improvements, and platform capabilities through Kanban systems.

Flow metrics help balance operational work with strategic initiatives.

Site Reliability Engineering

SRE teams often deal with unpredictable operational work.

Kanban helps prioritize incidents, manage operational load, and balance reliability improvements with reactive work.

Product Development

Product teams use Kanban to visualize discovery, design, development, validation, and release activities.

This provides transparency across the entire product lifecycle.

Service Teams

Customer support, IT operations, security, and business services frequently use Kanban to improve responsiveness, reduce waiting times, and optimize service delivery.

Comparison

🔗 How These Concepts Work Together

Kanban provides a common language for managing work across technical and business functions.

By visualizing work, limiting WIP, measuring flow, and continuously improving the system, organizations deliver value more predictably while reducing waste and improving customer responsiveness.

🏛️ Architecture Insight

Architecture influences flow just as much as process.

Modular systems, loosely coupled services, automated pipelines, and clear platform boundaries reduce dependencies, shorten lead times, and enable work to move smoothly through the value stream.

7. Bringing Kanban Together

🎯 Core Idea

Kanban is not about managing tasks.

It is about continuously improving the system through better flow.

Kanban is often introduced as a visual board for tracking work.

While visualization is an essential practice, it is only the beginning.

The true purpose of Kanban is to understand how work flows through a system, identify constraints, reduce unnecessary waiting, and continuously improve the delivery of value.

Rather than prescribing a fixed process, Kanban encourages organizations to evolve their existing systems using evidence, observation, and incremental change.

7.1 Optimizing Flow

Flow represents the movement of value from request to delivery.

When work moves smoothly, customers receive value sooner.

When work becomes blocked, queued, or interrupted, delivery slows regardless of how busy individuals appear.

Optimizing flow requires balancing demand with system capacity.

Teams improve flow by:

• Limiting Work In Progress (WIP).
• Reducing queue sizes.
• Eliminating unnecessary handoffs.
• Removing bottlenecks.
• Automating repetitive activities.
• Continuously measuring flow metrics.

Request
    │
    ▼
Ready
    │
    ▼
Development
    │
    ▼
Review
    │
    ▼
Testing
    │
    ▼
Deployment
    │
    ▼
Customer Value

Every delay between these stages represents an opportunity for improvement.

📦 Kanban Insight

Improving flow often means reducing waiting—not increasing effort.

7.2 Kanban and Scrum

Kanban and Scrum are frequently presented as competing frameworks.

In reality, they solve different problems and complement one another.

Scrum provides an empirical framework for navigating complexity through iterative delivery.

Kanban improves the flow of work through continuous optimization.

Many organizations successfully combine both approaches.

Examples include:

• Using Scrum events alongside Kanban boards.
• Applying WIP limits within Sprints.
• Tracking Lead Time alongside Sprint metrics.
• Visualizing Sprint work with Kanban.
• Using flow metrics to improve Sprint predictability.

Rather than replacing Scrum, Kanban strengthens it by exposing delays and improving the movement of work.

7.3 Continuous Evolution

Unlike large-scale transformation initiatives, Kanban encourages organizations to improve gradually.

Each improvement is based on observation rather than assumption.

The process is continuous.

Observe
    │
    ▼
Measure
    │
    ▼
Improve
    │
    ▼
Observe

Over time, many small improvements create significant organizational change.

This philosophy reflects Lean Thinking and reinforces one of Kanban's core beliefs:

Evolutionary change is more sustainable than disruptive transformation.

🔗 How These Concepts Work Together

Flow reveals how work moves through the system.

Metrics expose constraints.

Small improvements reduce delays.

Continuous measurement validates progress.

Over time, organizations improve not through dramatic redesigns but through many incremental changes that collectively optimize the delivery of customer value.

🏛️ Architecture Insight

Architecture affects flow as much as process.

Reducing dependencies, simplifying integrations, improving deployment pipelines, and increasing automation all contribute to smoother flow, shorter lead times, and faster delivery of customer value.

8. Common Misconceptions

Kanban is intentionally lightweight, which often leads to misunderstandings.

The following misconceptions are among the most common.

Kanban is just a board

A Kanban board is only a visualization tool.

Kanban is a management method focused on improving flow through visualization, measurement, feedback, and continuous improvement.

Kanban has no rules

Kanban is flexible, but it is not unstructured.

Effective Kanban systems rely on explicit policies, WIP limits, flow metrics, and regular feedback loops.

Kanban means no planning

Planning remains essential.

Kanban encourages planning based on current demand, system capacity, and flow rather than fixed iterations.

High utilization improves productivity

Keeping every individual busy often increases waiting times and slows overall delivery.

Kanban optimizes system performance rather than individual utilization.

WIP limits reduce productivity

Limiting Work In Progress frequently increases throughput by reducing multitasking, context switching, and queue sizes.

Finishing work is usually more valuable than starting additional work.

Kanban replaces Scrum

Kanban and Scrum address different challenges.

Many organizations successfully combine both approaches.

Kanban improves flow.

Scrum structures empirical learning.

Kanban is only for support teams

Although widely used in operational environments, Kanban is equally valuable in product development, DevOps, Platform Engineering, Site Reliability Engineering, security, research, and business operations.

9. 💼 In Practice

Case Study: Reducing Lead Time Through Flow Optimization

A software organization noticed that new features regularly took more than six weeks to reach production.

Developers remained busy throughout the process.

Despite this, customers frequently complained about slow delivery.

The engineering team decided to analyze its workflow using Kanban.

Step 1 — Visualize the Workflow

The team created a Kanban board representing every stage of delivery.

They quickly discovered that work spent more time waiting than actively being developed.

The largest queues appeared before code review and testing.

Step 2 — Measure Flow

The team began tracking:

• Lead Time
• Cycle Time
• Throughput
• Work In Progress

The metrics confirmed that excessive WIP and long review queues were delaying delivery.

Step 3 — Introduce WIP Limits

Instead of starting new work immediately, the team limited the number of items allowed in development and review.

Developers focused on completing existing work before beginning additional tasks.

Queue sizes gradually decreased.

Step 4 — Improve Continuously

Over several months the team:

• Automated repetitive testing.
• Simplified review policies.
• Improved deployment pipelines.
• Reduced unnecessary handoffs.
• Monitored flow metrics regularly.

Delivery became significantly faster without increasing team size.

Results

Lessons Learned

The team concluded that:

• Visualizing work exposed hidden delays.
• Measuring flow identified bottlenecks objectively.
• Limiting WIP accelerated delivery.
• Smaller queues improved predictability.
• Continuous improvement produced sustainable long-term gains.

Remember

Kanban does not improve delivery by making people work harder.

It improves delivery by helping work move through the system more efficiently.

10. 💡 Did You Know?

Kanban means "visual signal"

The word Kanban (看板) comes from Japanese and literally translates to signboard or visual signal.

Toyota originally used Kanban cards to communicate demand between production stages, creating a Pull System that minimized waste and overproduction.

Most Lead Time is often waiting

Studies across software organizations consistently show that work spends much more time waiting in queues than being actively developed.

Reducing waiting frequently delivers greater improvements than increasing development speed.

WIP limits often increase throughput

Although limiting work may seem counterintuitive, reducing Work In Progress typically shortens Lead Time, improves focus, and increases the number of completed work items over time.

Kanban encourages evolutionary change

Unlike many organizational transformation approaches, Kanban does not require teams to replace existing roles or processes.

Improvement begins with the current system and evolves through continuous experimentation.

Flow metrics measure systems—not people

Lead Time, Cycle Time, Throughput, and WIP are intended to improve the performance of the system.

Using these metrics to evaluate individual performance usually encourages unhealthy behaviours and reduces trust.

Kanban is widely used beyond software

Organizations apply Kanban in healthcare, finance, manufacturing, legal services, education, marketing, research, customer support, and many other knowledge work environments.

Its principles apply wherever work flows through a system.

11. 📝 Key Takeaways

After completing this chapter, you should understand that:

• Kanban is a Lean method focused on improving the flow of value.
• Flow is more important than maximizing individual utilization.
• Visualization makes work, queues, and bottlenecks visible.
• Limiting Work In Progress reduces delays and improves delivery.
• Managing flow requires measuring how work moves through the system.
• Lead Time, Cycle Time, Throughput, WIP, and Flow Efficiency provide complementary insights into system performance.
• Evolutionary change enables sustainable improvement without disruptive transformation.
• Kanban complements Scrum by optimizing flow while Scrum optimizes empirical learning.
• Modern software organizations use Kanban across Product Development, DevOps, Platform Engineering, SRE, and service delivery.
• Continuous improvement emerges from observing the system, measuring outcomes, and making incremental changes.

Remember

Customers do not experience your backlog.

They experience your Lead Time.

Every unnecessary queue, delay, and handoff slows the delivery of value.

Kanban helps organizations continuously improve the flow of that value.

12. 📚 Further Reading

Continue With

The following chapters build upon the concepts introduced here:

• 103 - Extreme Programming (XP)
• 104 - Agile Estimation & Forecasting
• 201 - Product Discovery
• 301 - DevOps
• 302 - Continuous Delivery

Related Topics

Kanban

• Kanban: Successful Evolutionary Change for Your Technology Business — David J. Anderson
• Kanban from the Inside — Mike Burrows
• Essential Kanban Condensed — David J. Anderson & Andy Carmichael

Lean Thinking

• Lean Thinking — James P. Womack & Daniel T. Jones
• The Toyota Way — Jeffrey K. Liker
• This Is Lean — Niklas Modig & Pär Åhlström

Flow

• The Principles of Product Development Flow — Donald G. Reinertsen
• Factory Physics — Wallace J. Hopp & Mark L. Spearman

Modern Software Engineering

• Accelerate — Nicole Forsgren, Jez Humble & Gene Kim
• Team Topologies — Matthew Skelton & Manuel Pais
• The DevOps Handbook — Gene Kim, Jez Humble, Patrick Debois & John Willis

Systems Thinking

• Thinking in Systems — Donella H. Meadows
• The Goal — Eliyahu M. Goldratt

Looking Ahead

Kanban demonstrates how improving flow reduces delays, exposes bottlenecks, and enables continuous delivery of value.

Flow alone, however, is not sufficient.

Fast delivery without strong engineering practices eventually leads to poor quality, increasing technical debt, slower delivery, and reduced customer value.

The next chapter introduces Extreme Programming (XP), a framework that complements Scrum and Kanban by focusing on technical excellence through practices such as Test-Driven Development, Pair Programming, Continuous Integration, Refactoring, and collective code ownership.

Next Chapter

103 - Extreme Programming (XP)

Explore how XP enables Agile teams to sustain high-quality software delivery through disciplined engineering practices, rapid feedback, and continuous technical improvement.