POPM Iteration Execution Practice Question
During an iteration, a Product Owner notices that the team's burn-down chart is trending above the ideal line, indicating they may not complete all committed stories. What should the Product Owner do?
⚠ Common exam trap
The trap here is reacting to the burn-down trend by pushing for overtime or escalating, instead of using it as a trigger for collaborative scope management.
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
✓
Collaborate with the team to understand the cause and determine if scope should be adjusted or stories should be split.
When the burn-down chart shows the team may not complete committed work, the Product Owner should collaborate with the team to understand the cause and adjust scope or split stories. This maintains focus on value delivery and respects the team's capacity, rather than resorting to overtime or ignoring the signal.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Immediately ask the team to work overtime to get back on track.
Why it's wrong here
Asking for overtime is not a sustainable or recommended practice in SAFe. It can lead to burnout, decreased quality, and technical debt. The Product Owner should instead collaborate with the team to understand the cause of the trend and adjust scope or approach. Overtime as a first response undermines the principle of sustainable pace and does not address the underlying issue.
- ✗
Ignore the burn-down chart because it is only a team-level metric and not the Product Owner's concern.
Why it's wrong here
The Product Owner should be engaged with iteration progress to manage scope and value. Ignoring the burn-down chart abdicates responsibility for ensuring the iteration delivers on its goals. While the team owns the how, the Product Owner owns the what and why, and must be aware of progress to make informed decisions about scope adjustments. Disengagement can lead to missed commitments and misaligned expectations.
- ✗
Escalate to the Release Train Engineer to have the team's commitment reduced for the next iteration.
Why it's wrong here
Escalating for a commitment reduction is premature and does not address the current iteration. The Product Owner should first work with the team to understand and mitigate the current trend. Involving the Release Train Engineer may be appropriate for systemic issues, but the immediate need is to collaborate on scope or approach. Reducing future commitment without addressing the current situation may not help the team meet its current goals.
- ✓
Collaborate with the team to understand the cause and determine if scope should be adjusted or stories should be split.
Why this is correct
The Product Owner should work with the team to assess the situation. If the team is falling behind, the Product Owner can help by clarifying priorities, splitting stories, or descoping lower-value items. This collaborative approach maintains trust, respects the team's capacity, and ensures the iteration still delivers the most valuable outcomes. It aligns with the Product Owner's role in managing scope and value during Iteration Execution.
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.