# What is a kanban board? A guide for software teams

> A kanban board shows work as cards moving through columns. Learn how it works, how it differs from scrum and how software teams use it well.

A kanban board shows a team’s work as cards moving through columns. It makes the state of everything visible at a glance, and it limits how much is in progress at once.

Web page: https://kansohq.app/guides/what-is-a-kanban-board

Updated: 5 October 2026

## What a kanban board is

A kanban board is a visual map of work. Each piece of work is a card. Each stage the work passes through is a column. Cards move from left to right as the work moves on, so anyone can see what is waiting, what is being done and what is finished without asking.

“Kanban” is the Japanese word for a visual signal or card. The method comes from the Toyota production system, and software teams adopted it because software work is also invisible until you draw it.

## The parts of a board

- **Cards** are single pieces of work: a task, a bug, a small feature. A good card is small enough to finish in days, not weeks.
- **Columns** are the stages of your real process, for example To do, In progress, In review and Done.
- **Work-in-progress limits** cap how many cards can sit in a column at once. They are what turns a board from a list into a system.
- **Priorities and owners** say which card matters most and who is doing it.

## The four habits of kanban

1. **Make the work visible.** If it is not on the board, it is not being tracked.
2. **Limit work in progress.** Finish things before starting new ones. Too much in progress means everything is slow.
3. **Manage the flow.** Watch where cards pile up. A pile is a bottleneck, and the bottleneck is where to put effort.
4. **Improve it a little at a time.** Change one rule, see what happens, repeat.

## Kanban and scrum

Kanban and scrum are often compared. Scrum organizes work into fixed-length sprints with set roles. Kanban has no fixed cycle: work flows continuously and the limits keep it steady. Many teams mix the two.

|  | Kanban | Scrum |
| --- | --- | --- |
| Rhythm | Continuous flow | Fixed-length sprints |
| Roles | None required | Product owner, scrum master, developers |
| Changing the plan | Any time, if a slot is free | Protected during a sprint |
| Main measure | Time a card takes to finish | Work completed per sprint |

## A board for a software team

A common setup is Backlog, To do, In progress, In review and Done. Add a column only when work genuinely waits there: a column nobody uses is noise. Put a limit on In progress and In review first, because that is where work tends to pile up.

## When a kanban board works best

- Work arrives unpredictably, like support requests, bugs and small improvements.
- The team wants to see the whole picture without ceremonies.
- People are tempted to start many things and finish few.

It works less well as the only tool for long projects with many dependencies. There, pair the board with a [release page](https://kansohq.app/product/releases.md) that shows the dates and what is blocked.

## The numbers worth watching

A board produces data for free. You do not need dashboards; you need three numbers and the habit of looking at them.

| Measure | What it is | What it tells you |
| --- | --- | --- |
| Cycle time | How long a card takes from started to done | How predictable the team is, and where work waits |
| Work in progress | How many cards are started and not finished | Whether the team is starting more than it finishes |
| Age of work in progress | How long each open card has been open | Which cards are stuck right now |

Start with the third. Walk the board each morning from right to left, from nearly done to just started, and ask of each old card: what would it take to finish this today?

## Swimlanes, and when to skip them

A swimlane is a horizontal band across the board that groups cards, for example by team, by product area or by kind of work. They help when several teams share one board and need to see their own work. They hurt when they multiply: a board with four columns and six lanes is a table nobody reads. Prefer filtering or saved views to extra lanes.

## Common mistakes

- **Cards that are really projects.** A card that stays in progress for a month is a project. Break it into cards that finish.
- **A Done column that is never cleared.** Archive finished work on a schedule, so Done shows what happened this week.
- **No limit anywhere.** Without a limit, a board is a to-do list with extra steps.
- **One person updating everyone’s cards.** If the board is kept by a manager, it will be out of date by lunch. Everyone moves their own.

## A kanban board in Kanso

Every project can hold a [Kanso board](https://kansohq.app/product/boards.md): columns you name, cards with a priority, an owner, a due date and acceptance criteria, and a work-in-progress limit on a column that warns when it is passed. The same cards also open as a table, list, timeline or calendar, so you can look at the work the way you need. See [how to set up a kanban board](https://kansohq.app/guides/how-to-set-up-a-kanban-board.md).

## Questions

### What is a kanban board?

A kanban board is a visual way to manage work. Each task is a card, each stage of the process is a column, and cards move across the board as work progresses.

### What are the columns on a kanban board?

They match your real process. A common set for software teams is Backlog, To do, In progress, In review and Done. Add one only when work genuinely waits there.

### What is a work-in-progress limit?

A cap on how many cards may be in a column at once. It stops the team from starting more than it can finish and shows where work is stuck.

### Is kanban better than scrum?

Neither is better for everyone. Kanban suits steady, unpredictable work and needs little ceremony; scrum suits teams that want fixed cycles and planned commitments. Many teams use parts of both.

## Keep reading

- [How to set up a kanban board for a software team](https://kansohq.app/guides/how-to-set-up-a-kanban-board.md): Set up a kanban board in eight steps: map your process, choose columns, size cards, set limits and review weekly. Includes column sets for software teams.
- [How to run a bug tracking board that stays tidy](https://kansohq.app/guides/bug-tracking-board.md): Run a bug tracking board that does not turn into a graveyard: what a bug card needs, how to triage, how to rank bugs and when to close them.
- [The MoSCoW method: Must, Should, Could explained](https://kansohq.app/guides/moscow-prioritization.md): The MoSCoW method sorts work into Must, Should, Could and Won’t. Learn what each means, how much to put in Must and how software teams use it.
- [Sprint planning template: goal, work and risks | Kanso](https://kansohq.app/templates/sprint-plan.md): A sprint planning template with the sprint goal, committed work, stretch, risks and what is out of scope. Copy it, or start it in Kanso.
- [Bug report template: steps, expected, actual | Kanso](https://kansohq.app/templates/bug-report.md): A bug report template with a summary, steps to reproduce, expected and actual results and an environment table. Copy it, or start it in Kanso.

## Parts of Kanso used

- [Kanso Boards](https://kansohq.app/product/boards.md): A board for each piece of work. Cards carry a priority, an owner, a due date and the criteria that say when they are done.
- [Kanso Calendar](https://kansohq.app/product/calendar.md): Due dates land on the calendar by themselves. Your open tasks sit beside the week, sorted by how much they matter.

[Kanso home, with plans and prices](https://kansohq.app/index.md)