CAPM Agile Frameworks and Methodologies Practice Question
In a Kanban system, the team notices that work items are spending too much time in the 'In Progress' column. Which practice should the team adopt to improve flow?
⚠ Common exam trap
PMI often tests the misconception that increasing WIP limits or removing columns will 'simplify' the process, when in fact the correct Kanban response to a bottleneck is to enforce stricter limits to expose and resolve the constraint.
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
✓
Set a strict WIP limit for the 'In Progress' column.
Setting a strict Work In Progress (WIP) limit for the 'In Progress' column directly addresses the bottleneck by capping the number of items the team can work on simultaneously. This forces the team to finish existing work before pulling new items, reducing multitasking and cycle time. In Kanban, WIP limits are the primary mechanism to expose flow inefficiencies and improve 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.
- ✗
Use longer development cycles.
Why it's wrong here
Longer development cycles extend each item's dwell time, so work remains in 'In Progress' even longer. Kanban improves flow by reducing batch size and cycle time, not extending them. Longer cycles would fit predictive, plan-driven delivery where scope is fixed far in advance.
- ✗
Increase the number of items allowed in the 'In Progress' column.
Why it's wrong here
Raising the work-in-progress limit admits more concurrent items, worsening congestion in the 'In Progress' column rather than relieving it. Limiting WIP is the Kanban mechanism that exposes bottlenecks and pulls flow. Increasing the limit would suit a team with idle capacity and no queueing delay.
- ✗
Remove the 'In Progress' column to simplify the board.
Why it's wrong here
Deleting the column hides the queue rather than resolving it; items still require development, so the delay simply becomes invisible. Kanban improves flow by visualising stages and limiting WIP. Removing a column would suit a board whose stages no longer match the actual workflow.
- ✓
Set a strict WIP limit for the 'In Progress' column.
Why this is correct
A strict WIP limit caps the number of items allowed in 'In Progress', forcing the team to finish existing work before pulling new items. This reduces multitasking and queueing, directly shortening the time items spend in that column.
Go deeper
Related to this question
About these practice questions
One of 451 original CAPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.