Scrum board vs Kanban board

A Scrum board and a Kanban board may look similar, but they manage work differently.

Area	Scrum board	Kanban board
Work cycle	Work is organized into fixed-length sprints	Work moves continuously
Board scope	Usually shows work selected for the current sprint	Shows the ongoing workflow
Planning	Sprint Planning selects work before the sprint begins	Work is pulled when capacity becomes available
Changes	Sprint scope is normally protected during the sprint	New work can be added and prioritized continuously
WIP limits	Helpful but not required by Scrum	A central Kanban practice
Board reset	Usually starts fresh for each sprint	Continues without resetting
Main metrics	Velocity, sprint burndown, sprint goal progress	Lead time, cycle time, throughput, WIP
Roles	Product Owner, Scrum Master, Developers	No required Kanban-specific roles
Delivery	Often reviewed at the end of the sprint	Items may be delivered whenever they are ready

Scrum board example

During a two-week sprint:

Sprint Backlog → To Do → In Progress → Review → Done

Only the stories selected for that sprint normally appear on the board.

At the end of the sprint:

For a support team:

Requested → Ready → In Progress (WIP 3) → Review (WIP 2) → Done

When one item moves to Done, the team pulls another item into the available space.

There is no need to wait for the next sprint.

Both boards:

The difference is not mainly the appearance of the board. The difference is how work is planned and controlled.

A Scrum board manages work inside a sprint. A Kanban board manages the continuous flow of work.

A Scrum team can also use Kanban practices such as WIP limits. This hybrid use is sometimes called Scrumban.

REF: AI Tools/ChatGPT