Kanban originated at Toyota in the 1940s as a visual system for managing manufacturing flow and reducing waste, later adapted for software and knowledge work by David J. Anderson in his book Kanban: Successful Evolutionary Change for Your Technology Business. Anderson’s Kanban Method formally defines four foundational principles alongside six general practices. This guide covers all four principles plus the single practice most teams treat as functionally foundational: limiting work in progress.
A note on accuracy: the canonical Kanban Method defines exactly four principles, not five. The fifth item below — Limit Work in Progress — is technically classified as one of Anderson’s six general practices, not a principle. It earns inclusion here because it is the single most defining, signature discipline of Kanban, and most practitioners treat it as foundational in practice even though Anderson’s own taxonomy places it a level below the four core principles.
What Is Kanban?
Kanban is a visual workflow management method that uses a pull system to limit work in progress and expose bottlenecks, adapted from Toyota’s manufacturing floor into a framework for software and knowledge work by David J. Anderson. Unlike time-boxed Agile frameworks such as Scrum, Kanban has no fixed iterations — work flows continuously, pulled into progress only when capacity exists to handle it.
What Are the Core Principles of the Kanban Method?
Kanban’s four core principles guide how a team adopts the method without disrupting existing operations: start with current processes, pursue incremental change, respect existing roles, and encourage leadership at every level. A fifth item, limiting work in progress, is added here as the practice most closely tied to Kanban’s core identity.
1. Start With What You Do Now
This principle instructs teams to begin Kanban adoption using their current processes and roles exactly as they are, rather than redesigning the workflow before making any changes. Kanban is explicitly non-disruptive by design — visualization and small adjustments come first, and larger process change follows only once the current system’s real behavior is understood.
2. Agree to Pursue Incremental, Evolutionary Change
This principle commits the team to gradual, continuous improvement rather than a single sweeping transformation. Organizations with a history of resistance to large-scale change, or with internal politics that make dramatic restructuring risky, benefit most directly from this evolutionary approach.
3. Respect Current Roles, Responsibilities, and Job Titles
This principle preserves existing roles and job titles during initial Kanban adoption, recognizing that current structures likely contain elements worth keeping and that forcing new titles onto people can generate unnecessary fear and resistance. Kanban does not require an organization to adopt new role names the way some other Agile frameworks do.
4. Encourage Acts of Leadership at All Levels
This principle distributes leadership responsibility across every team member, not just formal managers, encouraging anyone with insight into a process problem to take initiative in addressing it. This connects Kanban directly to servant leadership, since both models treat leadership as a distributed behavior rather than a title held by one person.
5. Limit Work in Progress (WIP)
Limiting work in progress caps the number of tasks a team works on simultaneously, forcing completion of existing work before new work begins and exposing bottlenecks that would otherwise stay hidden. This is the practice most people associate with Kanban visually — a board with columns capped at a maximum card count — and it is the mechanism that makes the other four principles operationally effective rather than purely philosophical.
How Does Kanban Differ From Scrum?
Kanban uses continuous flow with no fixed iterations and no prescribed roles, while Scrum organizes work into fixed-length sprints with defined roles like Scrum Master and Product Owner. A team can pull a single item into Kanban at any time; a Scrum team commits to a batch of work at the start of a sprint and holds that commitment until the sprint ends.
- Kanban — continuous flow, WIP limits, no fixed roles or ceremonies required.
- Scrum — fixed-length sprints, defined roles, structured ceremonies (planning, stand-up, review, retrospective).
How Do You Apply Kanban Principles When Leading an Agile Team?
Applying Kanban principles as a team lead means visualizing the current workflow first, setting a realistic WIP limit, and using acts of leadership from any team member to continuously surface and resolve process problems.
- Visualize the team’s actual current workflow before changing anything about it.
- Set a WIP limit low enough to expose bottlenecks without stalling throughput entirely.
- Encourage any team member to flag process problems, not only those in formal leadership roles.
- Review workflow policies regularly, adjusting incrementally rather than through large periodic overhauls.
How Does Kanban Appear on the PMI-ACP and PMP Exams?
The PMI-ACP exam tests Kanban directly as one of several Agile frameworks candidates must recognize and apply, while the PMP exam tests it more generally within its broader coverage of Agile and hybrid approaches. Candidates should expect scenario questions distinguishing Kanban’s continuous-flow model from Scrum’s iteration-based model.
Sample Question 1: A team wants to begin using Kanban without disrupting current operations or requiring anyone to change job titles. Which Kanban principle does this reflect? A) Encourage acts of leadership at all levels B) Start with what you do now C) Limit work in progress D) Agree to pursue incremental change
Sample Question 2: A Kanban board shows a column with significantly more cards than its WIP limit allows. What does this indicate? A) The team is performing exceptionally well B) A bottleneck exists at that stage of the workflow C) The WIP limit should be removed entirely D) The board is configured incorrectly and should be rebuilt
Sample Question 3: Which statement correctly distinguishes Kanban from Scrum? A) Kanban uses fixed-length sprints; Scrum uses continuous flow B) Kanban uses continuous flow with no fixed iterations; Scrum uses fixed-length sprints with defined roles C) Kanban requires a Scrum Master; Scrum does not D) Kanban and Scrum are identical frameworks with different names
Sample Question 4: A team member outside of a formal leadership role identifies a recurring process bottleneck and proposes a fix during a team discussion. Which Kanban principle does this reflect? A) Respect current roles, responsibilities, and job titles B) Encourage acts of leadership at all levels C) Start with what you do now D) Limit work in progress
Answers: 1) B — starting with current processes and preserving existing job titles reflects the “start with what you do now” principle. 2) B — a column exceeding its WIP limit is a direct visual signal of a bottleneck at that workflow stage. 3) B — Kanban’s continuous flow with no fixed iterations contrasts directly with Scrum’s fixed-length sprints and defined roles. 4) B — initiative from any team member, regardless of formal title, reflects the principle of encouraging leadership at all levels.
Frequently Asked Questions
Is Kanban Agile?
Kanban is widely considered part of the Agile family of methods, sharing Agile’s emphasis on flexibility and continuous improvement, though it predates the 2001 Agile Manifesto and originated in Lean manufacturing rather than software development specifically. Many organizations use Kanban as their primary Agile framework, either on its own or blended with Scrum.
Does Kanban Use Sprints?
Kanban does not use sprints — work flows continuously and is pulled into progress as capacity allows, in contrast to Scrum’s fixed-length, time-boxed iterations. This is one of the clearest structural differences between the two frameworks.
What Is a WIP Limit?
A WIP (work in progress) limit is a maximum number of tasks allowed in a given stage of the workflow at one time, forcing the team to finish existing work before starting anything new. WIP limits are what make bottlenecks visible on a Kanban board rather than hidden inside a growing backlog of half-finished work.
Can Kanban and Scrum Be Combined?
Kanban and Scrum can be combined in a hybrid approach often called Scrumban, which layers Kanban’s continuous-flow visualization and WIP limits on top of Scrum’s defined roles and ceremonies. Teams adopt this blend when they want Scrum’s structure but find fixed sprint boundaries too rigid for their actual workflow
