Kanban for Beginners: Principles, Boards and WIP Limits

Kanban is one of the easiest Agile approaches to start and one of the hardest to master. It asks you to do three simple things: make work visible, limit how much you start, and keep improving how work flows. Because it does not require new roles or time-boxed iterations, many teams adopt it inside an existing process. This lesson explains how Kanban works, how to build a useful board and how to avoid the mistakes that turn a Kanban board into a decorated to-do list.

Where Kanban Comes From

The word kanban is Japanese for "signboard" or "visual card". It originated in the Toyota Production System, where cards signalled that a station needed more parts, so production was pulled by demand rather than pushed by forecast. David J. Anderson adapted these ideas to knowledge work in the mid-2000s, giving rise to the Kanban Method used by software and service teams today.

The Core Principles

The Kanban Method rests on a few foundational principles:

  • Start with what you do now. You do not need to redesign your process on day one. Model the current workflow honestly.
  • Agree to pursue incremental, evolutionary change. Small improvements are less threatening than a big-bang transformation.
  • Respect the current roles, responsibilities and job titles. Change grows from within rather than being imposed.
  • Encourage acts of leadership at every level. Anyone can suggest an improvement.

The Six Core Practices

  1. Visualise the workflow. Put all work items on a board with columns for each stage.
  2. Limit work in progress (WIP). Set a maximum number of items allowed in each stage.
  3. Manage flow. Watch how work moves, identify bottlenecks and act on them.
  4. Make policies explicit. Write down what "done" means for each column, how priority is decided and who may pull work.
  5. Implement feedback loops. Hold regular reviews of the board, delivery and service.
  6. Improve collaboratively, evolve experimentally. Use models and data to propose and test changes.

Building Your First Kanban Board

Step 1: Map the real workflow

Start with the stages work actually passes through, not the ideal process on a slide. A simple software team might have: Backlog, Ready, In Progress, Review, Testing, Done. A support team might use: New, Triage, Investigating, Waiting for Customer, Resolved.

Step 2: Make each card represent one piece of work

Cards typically show a title, an owner or assignee, a date started, and any blocking information. Keep cards roughly comparable in size. When items that take a month sit next to items that take an hour, flow metrics become hard to interpret, so split large items.

Step 3: Define column policies

For each column, write down entry and exit criteria. For example, "Ready" means acceptance criteria written and no open questions. "Done" means deployed and verified. Explicit policies reduce arguments and rework. They resemble the Definition of Done used in Scrum; see Increment and Definition of Done.

Step 4: Set WIP limits

Start with a limit slightly lower than the current average, for example the number of people in that stage plus one, then adjust. When a column is full, no new work enters it until something leaves. This is the part beginners resist most, and the part that delivers the most benefit.

Why WIP Limits Work

People intuitively believe that starting more work means finishing more work. In practice the opposite is true. When too many items are in progress:

  • Each item waits longer between touches.
  • Context switching consumes time.
  • Problems are discovered late because nothing finishes quickly.
  • Bottlenecks hide behind busy people.

Limiting WIP forces the team to finish before starting, which shortens the time each item takes. This relationship is described by Little's Law: average cycle time equals average WIP divided by average throughput. Reduce WIP while keeping throughput steady, and cycle time falls.

The Four Key Flow Metrics

MetricWhat it tells you
Cycle timeHow long an item takes from starting work to finishing
Lead timeHow long from the request arriving to delivery
ThroughputHow many items are finished per unit of time
WIPHow many items are in progress right now

A cumulative flow diagram, which stacks the number of items in each stage over time, shows bottlenecks as widening bands. For definitions, see Scrum Metrics Explained: Velocity, Cycle Time and Lead Time, and for using these numbers to predict delivery see Forecasting in Scrum and Agile.

Classes of Service and Prioritisation

Not all work is equally urgent. Many teams define classes of service such as expedite (drop everything, with a strict limit of one at a time), fixed date, standard and intangible. Making these classes explicit prevents every request from being labelled "urgent".

Kanban Meetings (Cadences)

Kanban has no mandated meetings, but effective teams use regular cadences:

  • Daily stand-up at the board, walking cards from right to left to focus on finishing.
  • Replenishment meeting to decide what enters the workflow next.
  • Delivery planning to coordinate releases.
  • Service delivery review to look at metrics and customer satisfaction.
  • Retrospective to improve the process.

Common Beginner Mistakes

  1. No WIP limits. Without limits it is just a task board.
  2. Ignoring blocked items. A blocked card should be marked clearly and discussed daily, not left to age. See Impediment Management.
  3. Too many columns. Twelve columns create handoff theatre; keep it as simple as the real process allows.
  4. Using the board as a surveillance tool. The board is for the team to manage flow, not for managers to monitor individuals.
  5. Never reviewing the data. The metrics are how Kanban teams learn.

Is Kanban Right for You?

Kanban suits work that arrives continuously and unpredictably, such as support, operations, maintenance and some content teams. It also suits teams who want to improve gradually without a full process change. If your work is product development with a stable team, you may prefer Scrum, or a combination; see Scrum vs Kanban and Scrumban.

Key takeaways
  • Kanban means visualising work, limiting WIP and managing flow.
  • Start from your real process and improve gradually.
  • WIP limits reduce cycle time by forcing the team to finish before starting.
  • Track cycle time, lead time, throughput and WIP, and review them regularly.

Related Lessons