What is Kanban Board?
A Kanban board is a visual project management tool that organises work items into columns representing stages of a workflow, helping teams track progress and limit work in progress.
Kanban Board: In Depth
The Kanban board originated in Toyota's manufacturing system in the 1940s as a way to visualise production flow and signal when new work should start. Software teams adopted it in the 2000s as a flexible alternative to Scrum's rigid sprint structure. Today, Kanban boards are one of the most widely used tools in software development, from enterprise teams running Linear or Jira to solo developers using sticky notes on a whiteboard.
A Kanban board consists of columns that represent the stages work passes through — commonly something like Backlog, To Do, In Progress, Review, and Done. Work items (cards) start in the leftmost column and move right as they progress. The visual layout makes it immediately obvious how much work is in each stage, where bottlenecks are forming, and which items are blocked. A card that has been sitting in In Progress for two weeks stands out in a way it never would in a text-based task list.
One of Kanban's core principles is Work in Progress (WIP) limits: a cap on the number of cards allowed in a column at one time. WIP limits force teams to finish work before starting new work, reducing context switching and revealing bottlenecks. When a column hits its limit, the team must resolve the constraint rather than piling on more work. This discipline often exposes systemic problems — a slow review process, a single bottleneck reviewer — that would otherwise be masked by constantly starting new tasks.
Codepylot's Kanban board extends the classic format with features designed for AI-assisted development. Columns include Icebox (a parking lot for ideas), Backlog, To Do, In Progress, Review, and Done. Cards show priority badges, story point estimates, epic indicators, and AI agent status. You can drag and drop stories between columns, use keyboard shortcuts for navigation, and bulk-select cards for mass operations. When an AI agent completes a story, it automatically moves the card to Review and starts a dev preview — so your board reflects actual code state, not just human updates.
Related Terms
User Story
A user story is a short, plain-language description of a software feature written from the end user's perspective, typically following the format: 'As a [user], I want [goal] so that [benefit].'
Sprint Planning
Sprint planning is an agile ceremony where a team selects user stories from the backlog to work on during an upcoming sprint, estimates effort, and commits to a sprint goal.
Story Points
Story points are a unit of measure used in agile development to estimate the relative effort, complexity, and uncertainty of user stories, typically using a Fibonacci sequence scale.
Definition of Done
Definition of done (DoD) is a team-agreed checklist of criteria that every user story must meet before it can be considered complete and accepted, ensuring consistent quality across all delivered work.
Backlog Grooming
Backlog grooming (also called backlog refinement) is the ongoing process of reviewing, prioritising, estimating, and adding detail to user stories in a product backlog before they are pulled into a sprint.
Related Resources
Put Kanban Board into Practice with Codepylot
Codepylot turns rough ideas into structured user stories and ships them with autonomous AI coding agents. Free plan includes 3 projects and AI story generation.
Get Started FreeFrequently Asked Questions
What is the difference between a Kanban board and a Scrum board?
A Scrum board is reset at the start of each sprint and shows only the stories committed to that sprint. A Kanban board is a continuous flow board with no fixed time boxes — work items flow through whenever capacity is available. Scrum boards are better for teams that plan in sprints; Kanban boards suit teams with continuous incoming work or less predictable workloads.
How many columns should a Kanban board have?
Most software teams use five to seven columns: something like Backlog, To Do, In Progress, Review, and Done, with optional columns like Icebox or Blocked. Fewer columns reduce complexity; more columns add granularity. The right number is whatever accurately represents your team's actual workflow stages without creating unnecessary handoffs.
What are WIP limits and why do they matter?
Work in Progress (WIP) limits cap the number of cards allowed in a column at one time. They prevent teams from starting too many tasks simultaneously, which causes context switching and delays. When a column hits its WIP limit, team members must help finish existing work before picking up anything new. This discipline typically improves flow, reduces cycle time, and surfaces bottlenecks.