POPM Iteration Execution Practice Question
A Product Owner observes that the team's iteration burndown chart shows a flat line for the first half of the iteration, followed by a steep drop in the second half. What does this pattern most likely indicate, and what should the PO do?
⚠ Common exam trap
The trap here is interpreting the flat-then-steep burndown as over-commitment or a charting error, rather than recognizing it as a symptom of batching and delayed completion.
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 is batching work and not finishing stories until late; the PO should encourage smaller batches and finishing work earlier.
A flat burndown followed by a steep drop indicates that the team is holding work in progress and not completing stories until the end of the iteration. The Product Owner should encourage smaller batch sizes and finishing work incrementally, which improves flow, provides earlier feedback, and makes the burndown more linear.
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 is over-committed; the PO should reduce the number of stories in the iteration.
Why it's wrong here
Over-commitment would likely show a burndown that never reaches zero or a slow decline throughout. A flat line followed by a steep drop suggests delayed completion, not necessarily too much work. Reducing scope might help, but the core issue is batching. The PO should first address the team's working habits before adjusting the iteration scope.
- ✓
The team is batching work and not finishing stories until late; the PO should encourage smaller batches and finishing work earlier.
Why this is correct
A flat burndown followed by a steep drop typically indicates that the team is not finishing stories until the end of the iteration, often due to large work items or a reluctance to mark items done before all testing is complete. The PO should work with the team to slice stories smaller and encourage finishing work incrementally, which improves flow and provides earlier feedback.
- ✗
The team is not updating the burndown chart; the PO should remind them to update it daily.
Why it's wrong here
While inaccurate data is possible, the pattern of a flat line then steep drop is a common behavior when teams delay completion of work. The PO should first investigate whether the team is holding work in progress and not finishing until the end, rather than assuming a chart maintenance issue. The burndown is a reflection of work completion, not just a reporting tool.
- ✗
The team is experiencing too many dependencies; the PO should remove all dependencies from the iteration.
Why it's wrong here
Dependencies can cause delays, but the burndown pattern specifically points to work not being marked done until late. Removing all dependencies may not be feasible and could disrupt other teams. The PO should instead focus on helping the team finish work earlier and reduce batch size, while managing dependencies through the Program Board and coordination with other teams.
About these practice questions
Courseiva writes every POPM question from scratch — 336 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or 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.