POPM Product Owner and Product Management Roles Practice Question
A SAFe Product Owner is preparing for an upcoming Iteration Review. The team completed several stories, but one story was partially done. How should the Product Owner handle the partially done story during the Iteration Review?
⚠ Common exam trap
The trap here is believing that partially done work should be hidden or misrepresented, when the Iteration Review requires transparent inspection of the actual increment.
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
✓
Show the partial progress, explain why it is not complete, and discuss what remains to be done.
The Iteration Review is an inspect-and-adapt event where the team demonstrates the working increment and discusses any incomplete work. Transparency about partial progress enables stakeholder feedback and informed adaptation. Hiding or misrepresenting incomplete work undermines trust and the purpose of the review, which is to inspect the actual state and adjust the backlog.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Do not mention the partially done story; only discuss completed stories and update the team backlog accordingly.
Why it's wrong here
Omitting the partially done story hides important information from stakeholders and prevents a meaningful inspection of the team's actual progress. The Iteration Review should surface all relevant work, including incomplete items, so that stakeholders can provide feedback and the team can adapt. Ignoring it undermines transparency and the opportunity to learn.
- ✗
Move the partially done story back to the product backlog and remove it from the iteration's scope before the review.
Why it's wrong here
Moving the story back to the product backlog before the review does not change the fact that work was started but not finished. It also hides the actual state from stakeholders and prevents a discussion about what was learned. The Iteration Review is not about removing incomplete items but about inspecting the increment and adapting the backlog based on feedback.
- ✗
Demonstrate the partially done story as if it were complete to show progress to stakeholders.
Why it's wrong here
Demonstrating partially done work as complete misrepresents progress and violates transparency, which is a core SAFe principle. Stakeholders may make incorrect decisions based on false information, and the team loses trust. The Iteration Review is meant to inspect the actual increment, so only fully integrated and accepted stories should be demonstrated as done.
- ✓
Show the partial progress, explain why it is not complete, and discuss what remains to be done.
Why this is correct
This is the correct approach because the Iteration Review is an inspect-and-adapt event where the team demonstrates the working increment and discusses any incomplete work. Being transparent about partial progress allows stakeholders to give feedback, helps the team adjust the backlog, and maintains trust. It also aligns with SAFe's principle of transparency and the goal of continuous improvement.
About these practice questions
One of 336 original POPM practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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.