CAPM Agile Frameworks and Methodologies Practice Question
A Kanban team notices that cycle time is increasing despite stable demand. Which action is most likely to reduce cycle time?
⚠ Common exam trap
CAPM often tests the misconception that more people or higher WIP limits speed up delivery, when Little's Law shows that increasing WIP lengthens cycle time and the real fix is reducing queueing delays.
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
✓
Implement continuous integration to reduce integration delays.
Cycle time is the elapsed time from when work starts to when it finishes. When cycle time rises despite stable demand, the usual cause is queueing and waiting — work sits in progress waiting for integration, testing, or handoffs. Implementing continuous integration reduces the integration delay by merging and validating code frequently, shrinking the wait time that inflates cycle time. This is a flow-efficiency fix, not a capacity fix.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Add more developers to the team.
Why it's wrong here
Adding developers increases capacity but also increases the number of items in progress, and Kanban cycle time is governed by Little's Law, so throughput gains are offset by longer queues. It is tempting because extra staff conventionally speeds delivery, which holds when the constraint is capacity rather than excessive WIP.
- ✗
Use pair programming for all development tasks.
Why it's wrong here
Pair programming changes how work is performed, not how much work is in progress, so it does not address the queueing delay inflating cycle time. It is tempting because pairing can raise quality and reduce rework, which would be the right lever if defects, not WIP, were the bottleneck.
- ✗
Increase WIP limits to allow more work in progress.
Why it's wrong here
Raising WIP limits permits more concurrent items, lengthening each item's queueing delay and increasing cycle time further. It is tempting because higher limits feel like greater throughput, but Little's Law ties cycle time to WIP divided by throughput, so the correct action is to lower WIP limits and finish work.
- ✓
Implement continuous integration to reduce integration delays.
Why this is correct
Continuous integration shortens integration delays, a common hidden contributor to cycle time. This satisfies the stable-demand constraint: rather than adding capacity, the team removes the queueing and rework caused by deferred integration, so items flow through the board faster.
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.