1. Agile Delivery — Flow Efficiency & Bottlenecks
Before examining the choices, pause and recognize what this scenario is really testing.
When work begins piling up in “In Progress,” cycle time increases, and items stall, the instinct is often to react—push harder, add people, or widen the workflow.
But PMBOK‑8’s Delivery Performance domain teaches a different discipline: slow down, observe, and understand the flow before you intervene.
This question isn’t just about Agile mechanics; it’s about leadership maturity.
It asks whether you can distinguish between a reaction and a response.
Reactions chase symptoms. Responses diagnose causes. And in Agile delivery, the only way to restore momentum is to understand what’s blocking it.
This transition sets the stage for why the correct answer focuses on flow efficiency, bottlenecks, and root‑cause thinking—not quick fixes or escalation.
- Agile Delivery — Flow Efficiency & Bottlenecks
Midway through an Agile release, your team reports that although velocity appears stable, cycle time has increased and several items are stuck in “In Progress” for multiple days. The Product Owner is concerned and asks whether you should add more developers or increase WIP limits to push work through faster. According to PMBOK‑8’s Delivery Performance domain, what should you do FIRST?
Options
a)Increase WIP limits to allow more work to flow through the system. This is a reaction not a response. So incorrect.
- b) Add more developers to increase throughput. This is a reaction not a response. So incorrect.
- c) Conduct a flow efficiency analysis to identify bottlenecks and sources of delay. – I love this answer because it treats the situation the same way you would treat a problem in a relationship. In this relationship, you are Project Management for Agile Delivery. When something goes wrong, the first question shouldn’t be reactive or emotional — it should be soft, calm, and constructive: – “What can we do to resolve this?”
In PM terms, that translates directly to:
- Bottlenecks — What’s preventing us from moving forward?
- Sources of delay — Is the issue on my side, your side, or is there a third factor we need to remove from our path?
This mindset immediately drives you toward the root cause and the path to a real solution, not guesswork or premature escalation. That’s why this is the best answer — it reflects maturity, partnership, and disciplined problem‑solving.
- d) Escalate the issue to leadership for additional support. Almost never the answer to the question, so incorrect.
Correct Answer: c) Conduct a flow efficiency analysis
Explanation
- PMBOK‑8 emphasizes evaluation before intervention.
- Cycle time increases signal a flow problem, not a capacity problem.
- Flow efficiency analysis reveals where work is waiting, blocked, or constrained.
- Increasing WIP or Work in Process or adding developers without diagnosis worsens bottlenecks.
Thank you for participating. Please Like, Subscribe, and Comment for more content like this.
Access the full course:
Now available:
#PMCareerUSA #PMPExamPrepUSA
