In the Agile Practice Guide and Kanban methodology, the primary goal is to optimize the flow of work and increase efficiency by identifying and removing bottlenecks.
Why Choice C is correct:
WIP Limits: The project manager implements Work in Progress (WIP) limits. These are constraints placed on the number of work items that can be in a specific stage of the workflow (e.g., " In Development " or " Testing " ) at any given time.
Restricting Capacity: By restricting the maximum amount of activities, the team is forced to finish current tasks before starting new ones. This prevents the " multitasking trap " and ensures that work moves through the system faster.
Flow Management: If a column reaches its WIP limit, no new work can enter that stage. This makes bottlenecks immediately visible, allowing the team to collaborate (or " swarm " ) to clear the blockage.
Analysis of other options:
A (Capacity limit): While " capacity " is what is being managed, " Capacity limit " is not the formal technical term used in Kanban. The specific mechanism used to enforce that limit is called a WIP limit.
B (Pull system): A pull system is the result of using WIP limits. In a pull system, a team member only " pulls " new work into a column when there is available capacity (i.e., when they are below the WIP limit). It describes the movement of work, not the restriction itself.
D (Virtual board): This is simply the tool (like Jira, Trello, or a physical whiteboard) used to visualize the work. While the board displays the WIP limits, the board itself is not the element being " handled " to restrict the work.
Key Concept: The Project Management Institute (PMI) emphasizes that in a Kanban approach, the focus is on Cycle Time and Throughput. By managing Work in Progress (Choice C), the project manager ensures the team doesn ' t become overwhelmed, leading to a more predictable and sustainable pace of delivery.
