Kanban Board: Visualize Your Workflow
A Kanban board is a visual system for managing work as it moves through a process, making bottlenecks obvious. It's used in software development to track features from 'To Do' to 'Done'.
THE MENTAL MODEL: A Kanban board is a visual map of your workflow. Think of it like an assembly line for tasks, where each station is a column on the board. Its purpose is to make the status of every work item visible to everyone, instantly highlighting where work is getting stuck.
HOW IT WORKS: The simplest board has three columns: To Do, In Progress, and Done. Tasks, represented by cards, start in 'To Do'. When work begins, the card moves to 'In Progress'. When finished, it moves to 'Done'. The core principle is limiting Work In Progress (WIP). Each active column (like 'In Progress') has a strict limit on the number of cards it can hold. If the 'In Progress' column has a WIP limit of 3 and already holds 3 cards, no new tasks can be started until one of the current tasks is completed and moved to the next column. This forces the team to finish work, not just start it.
WHEN TO USE IT: Kanban excels in managing a continuous flow of work, such as IT support tickets, bug fixes, or content pipelines where tasks arrive unpredictably. It's also effective for personal productivity, helping you visualize and manage your own tasks. Its flexibility is ideal for teams where priorities can shift frequently, as there are no fixed-length sprints.
WHEN NOT TO USE IT: If a project requires extensive upfront planning with a fixed scope and hard deadlines, a time-boxed approach like Scrum might be more suitable. Kanban's effectiveness collapses if the team lacks the discipline to respect WIP limits; the board degenerates into a simple to-do list, and its primary benefit of exposing system bottlenecks is lost.
ONE CANONICAL EXAMPLE: A software team's board has columns: Backlog, Ready for Dev, In Dev (WIP Limit: 3), In QA (WIP Limit: 2), and Done. If the 'In QA' column is full with 2 cards, developers can't move their completed code for testing. This makes the QA bottleneck visible to everyone. Instead of starting new features, developers might swarm to help with testing to clear the blockage, improving the entire system's flow.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.