POPM Iteration Execution Practice Question
During Iteration Execution, a Product Owner notices that a user story in the Team Backlog has grown significantly in complexity after a spike. The team estimates it will now take three times longer than originally planned. What should the Product Owner do first?
⚠ Common exam trap
The trap here is assuming that the iteration can be extended or that overtime is an acceptable way to absorb increased scope.
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
✓
Split the story into smaller, independently valuable slices and reprioritize the Team Backlog.
When a story grows in complexity, the Product Owner should first collaborate with the team to split it into smaller, valuable slices and then reprioritize the Team Backlog. This maintains the iteration timebox, protects flow, and ensures the team can still deliver incremental value. Extending the iteration or pushing overtime violates SAFe principles, and simply removing the story may sacrifice value that could be captured through slicing.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Remove the story from the iteration and replace it with a lower-value story that fits the original estimate.
Why it's wrong here
Simply swapping the story for a lower-value one may not address the underlying complexity and could reduce the iteration's business value. The Product Owner should first consider splitting the story to retain value. Removing it without attempting to slice it wastes the learning from the spike and may leave the team without meaningful work that aligns with the iteration goal.
- ✗
Extend the iteration by one week to accommodate the increased effort.
Why it's wrong here
Iterations are timeboxed and should not be extended; doing so undermines the cadence and the principle of fixed time, variable scope. SAFe emphasizes that the iteration boundary is fixed, and the Product Owner should adjust scope rather than duration. Extending the iteration also delays feedback and disrupts the ART's synchronization, making this an inappropriate response to a single story's growth.
- ✗
Ask the team to work overtime to complete the story as originally estimated.
Why it's wrong here
Overtime is unsustainable and often reduces quality, morale, and predictability. SAFe promotes sustainable pace and the use of capacity rather than heroics. The Product Owner's role is to manage scope and priorities, not to pressure the team into exceeding capacity. This option ignores the need to re-evaluate the story's size and value in favor of an unhealthy short-term fix.
- ✓
Split the story into smaller, independently valuable slices and reprioritize the Team Backlog.
Why this is correct
Splitting the story preserves flow and allows the team to deliver incremental value while keeping the iteration goal achievable. The Product Owner owns backlog prioritization, so reordering after splitting is appropriate. This aligns with SAFe's guidance to keep stories small and vertically sliced, and it respects the team's capacity without forcing a scope increase or abandoning the iteration goal.
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.