Kanban Boards vs Scrum Boards: Tool Comparison for PMP

Two Boards, Different Philosophies

Both Kanban boards and Scrum boards are visual management tools used in agile project management, and both appear on the PMP exam. At first glance, they look similar — columns representing workflow stages with cards representing work items moving left to right. But they embody fundamentally different approaches to work management, and the PMP exam tests whether you understand those differences.

Scrum Boards: Sprint-Based Work Tracking

A Scrum board is designed to track work within a time-boxed sprint. Its characteristics include:

• Reset each sprint — The board is cleared and repopulated at the start of every sprint with items from the sprint backlog
• Fixed scope per sprint — Once sprint planning is complete, the team commits to a set of items. No new work enters the sprint without exceptional justification.
• Columns represent sprint workflow — Typical columns: To Do, In Progress, Done. The board reflects the sprint's progress toward its goal.
• Burndown tracking — Scrum teams often pair the board with a sprint burndown chart showing remaining work over time.
• Cadence is fixed — Sprints have a consistent length (typically 1-4 weeks), and events (planning, review, retrospective, daily standup) occur on a regular schedule.

Kanban Boards: Continuous Flow Management

A Kanban board manages the continuous flow of work without time-boxed iterations. Its characteristics include:

• Persistent board — The board is never reset. Items flow continuously from "requested" through "in progress" to "done."
• WIP limits — Each column has a work-in-progress (WIP) limit that caps the number of items in that stage. This is the defining feature of Kanban. When a column hits its limit, no new work can enter until existing work moves forward.
• Pull-based system — Team members pull new work when they have capacity, rather than having work assigned to them at the start of a sprint.
• Cycle time tracking — Instead of velocity (Scrum), Kanban tracks cycle time — how long an item takes to move from start to finish. Lower cycle time indicates better flow.
• No required cadence — There are no mandated events. Teams hold planning and review meetings as needed, not on a fixed schedule.

Key Differences for the PMP Exam

The exam may present a scenario and ask which tool or approach is appropriate. Use these distinctions:

Cadence

Scrum operates in fixed-length sprints. Kanban operates in continuous flow. If the scenario mentions time-boxed iterations, it is Scrum. If it describes ongoing work without iteration boundaries, it is Kanban.

WIP Limits

Kanban explicitly limits work-in-progress at each workflow stage. Scrum limits WIP implicitly through the sprint commitment — the team only takes on what they believe they can complete within the sprint. If the scenario focuses on limiting concurrent work in specific process stages, it is Kanban.

Scope Management

In Scrum, scope is fixed for the sprint and changes are discouraged mid-sprint. In Kanban, new items can be added to the board at any time (subject to WIP limits). If the scenario involves frequent reprioritization and incoming work, Kanban is more appropriate.

Roles

Scrum defines specific roles: Product Owner, Scrum Master, and Development Team. Kanban does not prescribe roles — it overlays onto existing team structures. If a question asks about a team without defined Scrum roles, Kanban may be the better fit.

When to Use Each Board

Help the team choose the right tool:

• Use Scrum boards when — The team works on discrete deliverables in iterative cycles, needs predictable cadence, and benefits from sprint goals and regular retrospectives.
• Use Kanban boards when — Work arrives unpredictably (like support tickets or maintenance), the team needs to visualize and optimize flow, or the organization cannot commit to fixed-length iterations.
• Use both (Scrumban) when — The team wants sprint structure with Kanban's WIP limits and flow visualization. This hybrid is increasingly common and may appear on the exam.

Common Metrics

• Scrum: Velocity — Story points completed per sprint. Used for planning future sprints and forecasting.
• Kanban: Cycle time and throughput — Average time per item and items completed per time period. Used for flow optimization and forecasting.
• Both: Cumulative flow diagram — Visualizes work item counts across workflow stages over time. Useful for identifying bottlenecks in either approach.

Study Strategy

For the PMP exam, focus on understanding when each tool is appropriate rather than memorizing board layouts. PMI tests situational judgment: given this team, this work type, and this organizational context, which approach serves better?

Explore agile tool comparisons and scenario-based practice questions in our Agile and Hybrid topic modules. Understanding the nuances between these approaches is essential for the 50% of PMP questions that involve agile or hybrid contexts.