I always trip up on questions about Kanban and limiting the WIP. I understand the basic definition, but the exam questions often ask about what you should do when a specific bottleneck occurs. How do you actually 'Limit the WIP' in a real-world scenario? Does the PMI-ACP exam prefer a specific answer, like 'stop starting and start finishing' or 'add more resources to the bottleneck'? Any tips to get better at these types of questions would be great.
Limiting Work In Progress (WIP) requires halting the initiation of new tasks to focus existing resources on completing current items, thereby identifying the bottleneck and improving overall system flow without the inefficiency of adding unnecessary personnel.
3 answers
Listen, if you are looking for a silver bullet for the exam, here is the harsh reality: Limit the WIP means exactly what it says, but most people treat it like a suggestion rather than a constraint.
On the PMI-ACP, when a bottleneck occurs, they want to see if you prioritize flow. If you start pulling in new items, you are just cluttering the system. The correct approach is almost always to 'stop starting and start finishing.' This is the only way to expose the actual constraint. If you add people to a bottleneck without fixing the process, you just create a more expensive bottleneck. It is simple systems theory.
The exam will try to bait you with answers that involve 'increasing throughput by adding team members' or 'escalating to management.' Ignore those traps. Your goal is to keep the current cycle time tight. Focus on moving items through the bottleneck, not around it. If you keep your WIP limits firm, the team is forced to swarm, which is exactly the behavior the exam board wants to see. Stop overthinking it and keep the work in progress lean.
If you are looking for the 'PMI-ACP' way to handle bottlenecks, stop treating them like a math problem and start treating them like a process flow issue. The exam loves to test whether you understand the fundamental Agile principle of flow over utilization.
When a bottleneck hits, adding resources is almost always the wrong answer. Why? Because you are merely masking the inefficiency and increasing the cost of delay. If you want to master these questions, memorize this hierarchy of operations:
- First: Stop starting new work to prevent the queue from expanding.
- Second: Focus the team on clearing the existing work-in-progress to unblock the flow.
- Third: Analyze the root cause of the bottleneck to determine if the WIP limit was set too high or if the process itself is broken.
The exam is not asking you to be a hero who throws bodies at a problem. It is asking if you have the discipline to restrict the inflow while you fix the plumbing. If you choose 'add more resources,' you are essentially admitting you do not understand the cost of context switching. Be precise with your logic, and you will pass.
Kelly, your explanation regarding the cost of context switching is very illuminating. I was focusing too much on the math, but your clear process flow hierarchy provides exactly the structure I was missing.
Thanks for the advice, Kelly. I’ve been guilty of wanting to throw resources at things, so this perspective on flow over utilization really clears up why that approach often fails.
Experience across various global enterprises has taught me that the biggest mistake teams make is viewing WIP limits as a static boundary rather than a dynamic lever. For the purpose of the exam, you need to internalize the following mindset shift:
- Bottlenecks are opportunities: They provide data on exactly where your process flow is interrupted.
- Swarming: This is the preferred method for resolving a constraint. It involves cross-functional collaboration to clear the block, rather than just shifting tasks.
- Constraint Management: Do not add resources, as this usually causes more communication overhead. Instead, optimize the existing team's capability to move items through the specific blocked stage.
When you encounter these questions, look for the option that emphasizes collaboration and finishing work over resource allocation. The exam is testing your adherence to lean principles. If you focus on the 'stop starting and start finishing' mantra, you will find that the correct answers naturally reveal themselves because they are the only ones that respect the flow of the entire system. Stay patient with the process, and recognize that the limit is there to protect the team from cognitive overload, not to punish them. You have got this.
I really appreciate this breakdown, Kelly. The hierarchy of operations you mentioned is quite helpful. I often feel overwhelmed by these exam questions, but focusing on the WIP limits makes much more sense now.