Home > Resources > The Kanban Guide

The Kanban Guide

This guide contains the minimum set of rules for Kanban. Any use of the word Kanban in this document specifically means the holistic set of concepts contained in this guide. By reducing Kanban to its essential components, the hope is that this guide will be a unifying reference for the community. By building upon Kanban fundamentals, the strategy presented here can accommodate the full spectrum of value delivery and organizational challenges.

Table of Contents

Purpose of the Kanban Guide


The flow-based perspective of Kanban can enhance and complement the Scrum framework and its implementation. Teams can add complementary Kanban practices whether they are just starting to use Scrum or have been using it all along.The Kanban Guide for Scrum Teams is the result of a collaboration between members of the Scrum.org community and leaders of the Kanban community. Together, they stand behind The Kanban Guide for Scrum Teams. It is their shared belief that professional product development practitioners can benefit from the application of Kanban together with Scrum.

Definition of Kanban

Kanban is a strategy for optimizing the flow of value through a process that uses a visual, pull-based system. There may be various ways to define value, including consideration of the needs of the customer, the end-user, the organization, and the environment, for example.

Kanban comprises the following three practices working in tandem:

  • Defining and visualizing a workflow
  • Actively managing items in a workflow
  • Improving a workflow


In their implementation, these Kanban practices are collectively called a Kanban system. Those who participate in the value delivery of a Kanban system are called Kanban system members.

Relation to the Scrum Guide

This guide does not replace or discount any part of The Scrum Guide. It is designed to enhance and expand the practices of Scrum. This guide assumes the reader is operating a process using the Scrum framework. Therefore, The Scrum Guide applies in its entirety.

Definition of Kanban

Kanban (n): a strategy for optimizing the flow of value through a process that uses a visual, workin-progress limited pull system.

Why Use Kanban?

Central to the definition of Kanban is the concept of flow. Flow is the movement of potential value through a system. As most workflows exist to optimize value, the strategy of Kanban is to optimize value by optimizing flow. Optimization does not necessarily imply maximization. Rather, value optimization means finding the right balance of effectiveness, efficiency, and predictability in how work gets done:

  • An effective workflow is one that delivers what customers want when they want it.
  • An efficient workflow allocates available economic resources as optimally as possible to deliver value.
  • A more predictable workflow means being able to accurately forecast value delivery within an acceptable degree of uncertainty.

The strategy of Kanban is to get members to ask the right questions sooner as part of a continuous improvement effort in pursuit of these goals. Only by finding a sustainable balance among these three elements can value optimization be achieved.

Because Kanban can work with virtually any workflow, its application is not limited to any one industry or context. Professional knowledge workers, such as those in finance, marketing, healthcare, and software (to name a few), have benefited from Kanban practices.

Kanban Theory

Kanban draws on established flow theory, including but not limited to: systems thinking, lean principles, queuing theory (batch size and queue size), variability, and quality control. Continually improving a Kanban system over time-based on these theories is one way that organizations can attempt to optimize the delivery of value.


The theory upon which Kanban is based is also shared by many existing value-oriented methodologies and frameworks. Because of these similarities, Kanban can and should be used to augment those delivery techniques.

Some additional content on Kanban Theory:

Kanban Practices

Defining and Visualizing the Workflow

Optimizing flow requires defining what flow means in a given context. The explicit shared understanding of flow among Kanban system members within their context is called a Definition of Workflow (DoW). DoW is a fundamental concept of Kanban. All other elements of this guide depend heavily on how workflow is defined.

At a minimum, members must create their DoW using all of the following elements:

  • A definition of the individual units of value that are moving through the workflow. These units of value are referred to as work items (or items).
  • Defined points at which work items are considered to have started and to have finished.
  • One or more defined states that the work items flow through from started to finished. Any work items between a start point and an endpoint are considered work in progress (WIP).
  • A definition of how WIP will be controlled from started to finished.
  • Explicit policies about how work items can flow through each state from started to finished.
  • service level expectation (SLE), which is a forecast of how long it should take a work item to flow from started to finished.

Kanban system members often require additional DoW elements such as values, principles, and working agreements depending on the team’s circumstances. The options vary, and there are resources beyond this guide that can help with deciding which ones to incorporate.

The visualization of the DoW is called a Kanban board. By making the workflow transparent, the Kanban board is essential to processing knowledge that informs optimal workflow operation and facilitates continuous process improvement.


There are no specific guidelines for how a visualization should look as long as it encompasses the shared understanding of how value gets delivered. Consideration should be given to all aspects of the DoW (e.g., work items, policies) along with any other context-specific factors that may affect how the process operates. Kanban system members are limited only by their imagination regarding how they make flow transparent.

Actively Managing Items in a Workflow

Active management of items in a workflow can take several forms, including but not limited to the following:

  • Controlling WIP.
  • Avoiding work items piling up in any part of the workflow.
  • Ensuring work items do not age unnecessarily, using the SLE as a reference.
  • Unblocking blocked work.

A common practice is for Kanban system members to review the active management of items regularly. Although some may choose a daily meeting, there is no requirement to formalize the review or meet at a regular cadence so long as active management takes place.

Controlling Work In Progress

Kanban system members must explicitly control the number of work items in a workflow from start to finish. That control is usually represented as numbers or (preferably) slots/tokens on a Kanban board that are called WIP limits. A WIP limit can include (but is not limited to) work items in a single column, several grouped columns/lanes/areas, or a whole board.

A side effect of controlling WIP is that it creates a pull system. It is called a pull system because Kanban system members start work on an item (pulls or selects) only when there is a clear signal that there is capacity to do so. When WIP drops below the limit in the DoW, that is a signal to select new work. Members should refrain from pulling/selecting more than the number of work items into a given part of the workflow as defined by the WIP Limit. In rare cases, system members may agree to pull additional work items beyond the WIP Limit, but it should not be routine.

Controlling WIP not only helps workflow but often also improves the Kanban system members’ collective focus, commitment, and collaboration. Any acceptable exceptions to controlling WIP should be made explicit as part of the DoW.

Service Level Expectation


The SLE is a forecast of how long it should take a single work item to flow from start to finished. The SLE itself has two parts: a period of elapsed time and a probability associated with that period (e.g., “85% of work items will be finished in eight days or less”). The SLE should be based on historical cycle time, and once calculated, should be visualized on the Kanban board. If historical cycle time data does not exist, the best guess will do until there is enough historical data for a proper SLE calculation.

Improving the Workflow

Having made the DoW explicit, the Kanban system members’ responsibility is to continuously improve their workflow to achieve a better balance of effectiveness, efficiency, and predictability. The information they gain from visualization and other Kanban measures guide what tweaks to the DoW may be most beneficial.


It is common practice to review the DoW from time to time to discuss and implement any changes needed. There is no need, however, to wait for a formal meeting at a regular cadence to make these changes. Kanban system members can and should make just-in-time alterations as the context dictates. There is also nothing that prescribes improvements to workflow to be small and incremental. If visualization and the Kanban measures indicate that a big change is needed, that is what the members should implement.

Kanban Measures

The application of Kanban requires the collection and analysis of a minimum set of flow measures (or metrics). They are a reflection of the Kanban system’s current health and performance and will help inform decisions about how value gets delivered.

The four mandatory flow measures to track are:

  • WIP: The number of work items started but not finished (according to the DoW).
  • Throughput: The number of work items finished per unit of time. Note the measurement of throughput is the exact count of work items.
  • Work Item Age: The amount of elapsed time between when a work item started and the current time.
  • Cycle Time: The amount of elapsed time between when a work item started and when a work item finished.

In and of themselves, these metrics are meaningless unless they can inform one or more of the three Kanban practices. Therefore, visualizing these metrics using charts is recommended. It does not matter what kind of charts are used as long as they enable a shared understanding of the Kanban system’s current health and performance.


The flow measures listed in this guide represent only the minimum required for the operation of a Kanban system. Kanban system members may and often should use additional context-specific measures that assist data-driven decisions.

Some additional content on Kanban Measures, WIP, Throughput, Work Item Age, Work Item Aging, Cycle Time:


Kanban’s practices and measures are immutable. Although implementing only parts of Kanban is possible, the result is not Kanban. One can and likely should add other principles, methodologies, and techniques to the Kanban system, but the minimum set of practices, measures, and the spirit of optimizing value must be preserved.

History of Kanban

The present state of Kanban can trace its roots to the Toyota Production System (and its antecedents) and the work of people like Taiichi Ohno and W. Edwards Deming. The collective set of practices for knowledge work that is now commonly referred to as Kanban mostly originated on a team at Corbis in 2006. Those practices quickly spread to encompass a large and diverse international community that has continued to enhance and evolve the approach.


In addition to all who helped to develop Kanban over the years, we would like to thank the following individuals specifically for their contributions to this guide:

  • Yuval Yeret and Steve Porter for their initial contribution of foundational concepts.
  • Emily Coleman for the inspiration to broaden the definition of value.
  • Daniel Doiron and Steve Tendon for their contribution to key concepts.
  • Ryan Ripley and Todd Miller for helping to develop much of the supporting materials upon which this guide is based.
  • Julia Wester, Colleen Johnson, Jose Casal, and Jean-Paul Bayley for being insightful reviewers of the early drafts.
  • Dave West and Eric Naiburg for their careful consideration of what should be in the final published version.
  • Deborah Zanke for editing.


We believe that every company deserves high quality software delivered on a regular cadence that meets its customers needs. Our goal is to help you reduce your cycle time, improve your time to market, and minimise any organisational friction in achieving your goals.

naked Agility Limited is a professional company that offers training, coaching, mentoring, and facilitation to help people and teams evolve, integrate, and continuously improve.

We recognise the positive impact that a happy AND motivated workforce, that has purpose, has on client experience. We help change mindsets towards a people-first culture where everyone encourages others to learn and grow. The resulting divergent thinking leads to many different ideas and opportunities for the success of the organisation.