Definition
Board (Kanban Board)
A board is a visual layout that arranges work as cards in columns, where each column represents a stage of a workflow — typically backlog, in progress, and done. Cards move left to right as work advances. Boards make a team's flow visible at a glance, exposing where work sits, stalls, or piles up.
Key takeaways
- A board arranges work as cards in columns, where each column is a workflow stage and cards move left to right as work advances.
- Its instant value is shared situational awareness — anyone can glance and know what's in flight, waiting, or backing up.
- Columns map to the workflow states an issue tracker already defines, so the board is a view onto the same data, not a separate system.
- Boards aren't exclusive to Kanban — a sprint or cycle can be visualized on a board too, scoped to that iteration's items.
A board turns an abstract workflow into something you can see and touch. Each card is one unit of work; each column is a state that work passes through. The instant value is shared situational awareness — anyone can glance at the board and know what is in flight, what is waiting, and where the queue is backing up, without asking a single status question.
Columns usually map to the workflow states an issue tracker already defines, so the board is a view onto the same underlying data rather than a separate system. Dragging a card to a new column changes the issue's state; the board and the records stay in sync. Many boards add WIP limits per column, capping how many cards a stage may hold so the team finishes work before starting more.
Boards are most powerful for flow-based work, but they are not exclusive to Kanban — a sprint or cycle can be visualized on a board too, scoped to just that iteration's items. The board is the visualization; whether work runs continuously or in time-boxes is a separate choice.
In Planoda, every board is a drag-and-drop Kanban surface with optional per-column WIP limits and live flow metrics, rendered from the same issue data the rest of the workspace uses.
Related terms
- KanbanKanban is a visual workflow method that maps work onto a board of columns representing stages — typically backlog, in progress, and done. Cards move left to right as work advances. It emphasizes continuous flow, making bottlenecks visible, and limiting work in progress rather than committing to fixed time-boxes.
- WIP LimitA WIP (work-in-progress) limit is a cap on how many items may be active in a given workflow stage at once. By forcing a team to finish work before starting more, WIP limits expose bottlenecks, reduce context-switching, and shorten cycle time. They are the core mechanism that makes Kanban flow rather than pile up.
- BacklogA backlog is the ordered list of all work a team has identified but not yet started — features, bugs, improvements, and ideas. It is the team's single source of pending work, prioritized so the most valuable or urgent items sit at the top, ready to be pulled into a cycle or onto a board.
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.