CAPM Agile Frameworks and Methodologies Practice Question
A team is transitioning to Kanban. Which TWO principles should they adopt? (Choose two)
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
✓
Define process policies
Option B, define process policies, is correct because Kanban requires making work policies explicit (e.g., definition of done, entry/exit criteria, WIP limits per column) so that everyone understands how work flows and decisions are made. Option C, limit work in progress, is correct because constraining WIP is the core Kanban practice that exposes bottlenecks, reduces multitasking, and improves flow and cycle time. Options A (sprint reviews) and D (fixed-length iterations) belong to Scrum's timeboxed framework, not Kanban, which is continuous-flow and does not mandate iterations or sprint ceremonies. Option E (velocity tracking) is a Scrum metric based on story points completed per sprint; Kanban instead uses flow metrics such as cycle time, lead time, and throughput.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Sprint reviews
Why it's wrong here
Sprint reviews belong to Scrum's fixed-length iteration cadence, which Kanban replaces with continuous flow and on-demand delivery. Kanban principles instead emphasise visualising the workflow and limiting work in progress. Sprint reviews tempt teams migrating from Scrum who want to preserve existing ceremony schedules rather than adopt flow-based practices.
- ✓
Define process policies
Why this is correct
Defining process policies makes workflow rules explicit, satisfying Kanban's requirement that work states and transition criteria be visible. Policies specify entry and exit conditions for each column, limiting work in progress and standardising handoffs. This transparency enables the team to identify bottlenecks and improve flow systematically.
- ✓
Limit work in progress
Why this is correct
Limiting work in progress is a core Kanban practise that caps concurrent items per workflow stage, exposing bottlenecks and improving flow. It directly addresses the team's transition need by preventing overload, which is the principle Kanban prescribes for managing capacity and reducing cycle time.
- ✗
Fixed-length iterations
Why it's wrong here
Fixed-length iterations are Scrum's timeboxed sprints; Kanban delivers continuously without prescribing iteration boundaries. Adopting them reintroduces batch cadence rather than flow. Kanban principles instead emphasise visualising the workflow and limiting work in progress. Fixed iterations tempt teams migrating from Scrum who wish to retain familiar planning rhythms.
- ✗
Velocity tracking
Why it's wrong here
Kanban measures cycle time and throughput, deliberately avoiding velocity, which is a Scrum estimation artefact tied to story points and fixed iterations. Velocity tracking tempts teams migrating from Scrum who wish to retain familiar forecasting metrics, but Kanban's flow-based principles instead emphasise limiting work in progress and visualising the workflow.
Go deeper
Related to this question
About these practice questions
Courseiva writes every CAPM question from scratch — 451 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.