CAPM Practice: Determine how to prepare and execute task management steps
Question 1 of 60 in Determine how to prepare and execute task management steps
Pick an answer below — you'll get the explanation instantly, no signup.
Show answer & explanation
Correct answer: Limit the number of items being worked on simultaneously to improve flow and reduce context switching
Explanation
WIP limits constrain how many items can be in any given workflow state simultaneously (e.g., only 3 items can be 'In Progress' at once). This prevents multitasking, reduces context switching, surfaces bottlenecks when upstream items pile up waiting for a congested state, and encourages team members to help complete in-progress items rather than starting new ones. WIP limits improve flow efficiency.
**Why not A:** WIP limits have nothing to do with working hours. They constrain the number of work items in a given workflow state, not the time individuals spend working each day. Sustainable pace is a separate agile concept.
**Why not B:** WIP limits cap the number of items in progress, not the number of people assigned to a task. In fact, WIP limits often encourage multiple team members to swarm on in-progress items to finish them.
**Why not D:** WIP limits apply to active workflow states such as 'In Progress' or 'Testing', not to the product backlog. The backlog can hold any number of items, which the product owner refines and prioritizes.
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).
All 1,500+ CAPM questions are free
Sign up to track your progress, see detailed analytics, and get personalized study recommendations.
Sign Up Free