POPM Iteration Execution Practice Question
Exhibit
Iteration Burndown Chart: Day 1-4: Linear decline. Day 5: Flatline. Day 6: Spike (new stories added). Day 7-10: Stagnant remaining work.
Refer to the exhibit. As a PO, what does this pattern primarily suggest about the team's current iteration execution?
⚠ Common exam trap
Candidates often misidentify the pattern as 'high velocity' or 'agile flexibility,' failing to recognize that mid-iteration changes are a negative indicator of poor planning and lack of team protection.
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 iteration is suffering from scope creep and a lack of focus on completion.
The exhibit indicates significant instability in scope and flow. Adding stories mid-iteration disrupts the team's focus and prevents the completion of planned work, leading to the observed stagnation. This pattern signifies that the team is failing to protect their iteration from external changes, which is a critical responsibility of the PO and Scrum Master to ensure the team can meet their commitments.
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 excellent velocity and is effectively managing technical debt.
Why it's wrong here
The chart shows a flatline and stagnation, which is the opposite of excellent velocity. Effective teams show a consistent burndown. Technical debt management would be reflected in consistent progress, whereas this pattern shows teams struggling to finalize work, likely due to external interruptions or scope creep.
- ✗
The team is successfully utilizing the 'stretch goal' mechanism to maximize value.
Why it's wrong here
Stretch goals are meant to handle uncertainty, not to justify mid-iteration scope changes or stagnant progress. A spike in work suggests poor planning or failure to protect the iteration, while stagnant work indicates that the team is not effectively collaborating to complete the primary iteration commitment.
- ✓
The iteration is suffering from scope creep and a lack of focus on completion.
Why this is correct
Adding work mid-iteration is a clear indicator of scope creep. When combined with stagnant burndown, it reveals that the team is distracted and unable to finalize their committed stories. The PO must intervene to protect the iteration and stop the practice of adding new work mid-cycle.
- ✗
The team's velocity is intentionally throttled to accommodate architectural runway.
Why it's wrong here
Architectural runway is planned during PI Planning, not injected randomly causing burndown spikes. The behavior shown is reactive and disorganized rather than strategic. Throttling velocity for structural improvements would appear as planned capacity allocation, not as erratic spikes and stagnant work across the iteration timeline.
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.