Skip to content
CAPMMedium

CAPM Practice: Determine how to prepare and execute task management steps

Question 14 of 60 in Determine how to prepare and execute task management steps

Pick an answer below — you'll get the explanation instantly, no signup.

An adaptive team wants to reduce the time stories spend 'In Progress' without completion. What Kanban principle MOST directly addresses this?
Show answer & explanation

Correct answer: Implement WIP limits to prevent team members from starting new items before finishing current ones

Explanation

WIP limits directly target the 'in progress but not done' problem. When In Progress is limited (e.g., 'only 3 items can be In Progress simultaneously'), team members must complete current work before pulling new work. This concentrates attention, reduces context switching, and surfaces where items are truly stuck. WIP limits improve throughput by optimizing completion rate, not start rate.

**Why not A:** Velocity is a Scrum measure of completed work per sprint, not a Kanban principle. Trying to raise velocity does nothing to stop team members from starting new items before finishing current ones, so stories can still sit In Progress.

**Why not B:** Sprint length is a Scrum timebox, not a Kanban principle. Shorter sprints do not limit how many items are started at once, so work can still pile up In Progress, just across shorter timeboxes.

**Why not D:** Adding team members increases onboarding and coordination overhead and often increases the number of items started in parallel. It does not address the root cause, which is too much work in progress at once.

Key Concept

This question covers Determine how to prepare and execute task management steps under Determine how to prepare and execute task management steps (Agile Frameworks/Methodologies).

Share:

All 1,500+ CAPM questions are free

Sign up to track your progress, see detailed analytics, and get personalized study recommendations.

Sign Up Free