CAPM Agile Frameworks and Methodologies Practice Question
Which of the following is a key benefit of using a Kanban board?
⚠ Common exam trap
The trap is confusing Kanban with Scrum, leading candidates to select Scrum-specific elements like fixed iterations or defined roles as benefits of Kanban.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Visualizing the workflow.
A Kanban board's primary benefit is visualizing the workflow, making work items and their progress visible to everyone. This transparency helps identify bottlenecks, improve flow, and facilitate pull-based work. Fixed time iterations, sprint planning ceremonies, and defined roles like Product Owner are characteristics of Scrum, not Kanban.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Fixed time iterations.
Why it's wrong here
Fixed time iterations are Scrum sprints, whereas Kanban delivers continuously without prescribed iterations. It is tempting because many teams run Kanban inside sprints, but Kanban's benefit is making workflow and bottlenecks visible while limiting work in progress, not enforcing timeboxes.
- ✓
Visualizing the workflow.
Why this is correct
Kanban boards render every work item and its stage on a shared visual surface, exposing bottlenecks, work-in-progress limits and queue build-up that hidden backlogs conceal. This directly satisfies the stem's requirement for a key benefit: making workflow state and flow constraints immediately visible to the whole team.
- ✗
Sprint planning ceremonies.
Why it's wrong here
Sprint planning ceremonies belong to Scrum's timeboxed framework, not Kanban, which uses continuous flow with replenishment and no sprint events. It is tempting because both are agile approaches, yet Kanban's benefit is visualising work in progress and limiting WIP, not scheduling ceremonies.
- ✗
Defined roles such as Product Owner.
Why it's wrong here
Defined roles such as Product Owner are Scrum accountabilities, not a Kanban feature; Kanban prescribes no roles. It is tempting because agile boards often sit within Scrum teams, but Kanban's benefit is flow-based visualisation and explicit WIP limits, independent of any role structure.
Go deeper
Related to this question
About these practice questions
This CAPM question is part of Courseiva's 451-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official PMI exam blueprint
This CAPM practice question is part of Courseiva's free PMI certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CAPM exam.