POPM Iteration Execution Practice Question
A Product Owner is reviewing the team's Iteration Burndown chart mid-iteration and sees that the remaining work line is flat for several days, even though the team reports they are working on multiple stories simultaneously. What is the most likely explanation and the best PO action?
⚠ Common exam trap
The trap here is attributing a flat burndown to estimation errors or external blockers rather than recognizing the internal symptom of too much work in progress.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The team has too many stories in progress, causing delays in completion; the PO should help the team limit WIP and finish stories before starting new ones.
A flat Iteration Burndown chart during active work usually means stories are started but not completed, often due to excessive work in progress. The Product Owner should work with the team to limit WIP, encourage swarming, and focus on finishing stories to achieve a steady burndown. This aligns with SAFe's emphasis on flow and continuous delivery.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The team has too many stories in progress, causing delays in completion; the PO should help the team limit WIP and finish stories before starting new ones.
Why this is correct
A flat burndown while the team works on many stories simultaneously typically signals excessive WIP, which delays value delivery. The Product Owner should collaborate with the team to enforce WIP limits and encourage finishing work before pulling new items. This improves flow and makes progress visible on the burndown chart.
- ✗
The team is blocked by external dependencies; the PO should escalate to the Release Train Engineer immediately.
Why it's wrong here
External dependencies can cause delays, but the scenario specifically mentions the team is working on multiple stories simultaneously, which points to internal WIP issues. Escalating without first addressing the team's own working agreements may be premature. The PO should first help the team improve their flow before escalating.
- ✗
The team is not updating the burndown chart; the PO should mandate daily updates.
Why it's wrong here
While updating the chart is important, a flat line with simultaneous work often indicates work-in-progress (WIP) is too high, not simply a charting issue. Mandating updates treats a symptom, not the root cause. The PO should investigate why stories aren't being completed rather than assuming a reporting problem.
- ✗
The team is overestimating story points; the PO should recalibrate estimates for the next iteration.
Why it's wrong here
Overestimation would cause the burndown to drop faster than expected, not remain flat. A flat line indicates no stories are being completed, which is more about flow than estimation accuracy. Recalibrating estimates does not address the immediate issue of work not finishing.
About these practice questions
This POPM question is part of Courseiva's 336-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Scaled Agile exam blueprint
This POPM practice question is part of Courseiva's free Scaled Agile certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the POPM exam.