The Kanban Board: Visualizing Workflow

Level: Intermediate Module: Kanban for Scrum Teams 3 min read Lesson 36 of 52

Overview

  • What you’ll learn: How to design an effective Kanban board, the difference between workflow states and board columns, common board anti-patterns, and how to evolve your board as your process matures.
  • Prerequisites: Lessons 33–35.
  • Estimated reading time: 14 minutes

Introduction

The Kanban board is the most visible element of Kanban, and therefore the most misunderstood. A board is not Kanban. A board is a tool that makes your workflow visible. The quality of the board determines the quality of the transparency — and therefore the quality of your inspect-and-adapt cycle.

Anatomy of a Kanban Board

A basic Kanban board has columns representing workflow states. Each card on the board represents a work item. Cards move from left to right as work progresses.

A minimal board might look like: To Do → In Progress → Done. But this oversimplification hides important states. A better board might be: Backlog → Ready → In Development → Code Review → Testing → Done.

The key principle: each column should represent a distinct state where work actually sits. If work routinely sits waiting for code review, that wait state should be visible on your board.

Explicit Policies

Each column should have explicit entry and exit criteria. For example:

  • Ready: Item has acceptance criteria, is sized, and is independent enough to work on.
  • In Development: A developer has started working on it. WIP limit: 5.
  • Code Review: Pull request submitted, passes CI. WIP limit: 3.
  • Testing: Code merged to staging. Manual or automated verification in progress.
  • Done: Meets Definition of Done. Deployed or ready to deploy.

These policies should be visible — written directly on the board or on a nearby poster. If people have to ask “when does a card move to the next column?” your policies are not explicit enough.

Common Board Anti-Patterns

  1. The Wallpaper Board: Hasn’t been updated in weeks. Decorative, not functional.
  2. The Dumping Ground: No WIP limits, 40 items in “In Progress.” This is a to-do list, not a Kanban board.
  3. The Three-Column Trap: To Do / Doing / Done — hides all intermediate states and makes bottlenecks invisible.
  4. The Rainbow Board: So many swim lanes, colors, tags, and labels that nobody can tell what is important.

Physical vs. Digital Boards

Physical boards (whiteboards, sticky notes) are excellent for co-located teams: they are always visible, encourage interaction, and are tactile. Digital boards (Jira, Trello, Azure DevOps) are necessary for remote teams and provide metrics automatically.

The best choice depends on your context. Many teams use both: a physical board for daily standups and a digital board for metrics and remote access.

Key Takeaways

  • Board columns represent workflow states, not just progress stages.
  • Make policies explicit — entry and exit criteria for each column.
  • Avoid anti-patterns: wallpaper boards, dumping grounds, three-column traps.
  • Choose physical or digital (or both) based on team context.
本課中文版

概述

看板是看板方法中最可見的元素，因此也是最被誤解的。板子不是看板。板子是讓你的工作流程可見的工具。

看板的構造

基本的看板有代表工作流程狀態的欄位。最簡單的板子可能是：待辦 → 進行中 → 完成。但這種過度簡化隱藏了重要狀態。更好的板子：待辦清單 → 就緒 → 開發中 → 程式碼審查 → 測試 → 完成。

明確的政策

每一欄都應該有明確的進入和退出標準。這些政策應該是可見的——直接寫在板子上。如果人們需要問「卡片什麼時候移到下一欄？」那你的政策不夠明確。

常見的板子反模式

  1. 壁紙板：好幾週沒更新。裝飾用的，不是功能性的。
  2. 垃圾場板：沒有 WIP 限制，40 個項目在「進行中」。
  3. 三欄陷阱：待辦 / 進行中 / 完成——隱藏所有中間狀態。
  4. 彩虹板：太多泳道、顏色、標籤，沒人看得出什麼重要。

重點整理

  • 欄位代表工作流程狀態，不只是進度階段。
  • 讓政策明確——每一欄的進入和退出標準。
  • 避免反模式：壁紙板、垃圾場、三欄陷阱。
日本語版

概要

カンバンボードはカンバンの最も目に見える要素であり、最も誤解されている。ボードはカンバンではない。ボードはワークフローを可視化するツールだ。

カンバンボードの構造

基本的なボードにはワークフローの状態を表す列がある。最小限のボード：To Do → In Progress → Done。しかしこの過度な単純化は重要な状態を隠す。より良いボード：バックログ → 準備完了 → 開発中 → コードレビュー → テスト → 完了。

明示的なポリシー

各列には明示的な入口・出口基準が必要だ。これらのポリシーは目に見えるようにすべき——ボード上に直接書くこと。

一般的なボードのアンチパターン

  1. 壁紙ボード：何週間も更新されていない。装飾であり、機能的ではない。
  2. ゴミ捨て場ボード：WIP制限なし、40項目が「進行中」。
  3. 3列の罠：To Do / Doing / Done——すべての中間状態を隠す。
  4. レインボーボード：スイムレーン、色、タグが多すぎて何が重要か分からない。

重要ポイント

  • 列はワークフローの状態を表し、単なる進捗段階ではない。
  • ポリシーを明示的にする——各列の入口・出口基準。
  • アンチパターンを避ける：壁紙ボード、ゴミ捨て場、3列の罠。

You Missed