POPM PI Planning Preparation Practice Question
A Product Manager is facilitating a pre-PI Planning meeting with stakeholders to review the draft PI Objectives. One stakeholder insists on adding a new feature that was not previously prioritized. What should the Product Manager do?
⚠ Common exam trap
The trap here is thinking that any new feature must be immediately added to the current PI, when it should be evaluated and possibly deferred to the next PI.
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
✓
Evaluate the feature against the current PI Objectives and, if it aligns with the ART's vision, work with the stakeholder to prioritize it for the next PI.
The Product Manager should evaluate the new feature against the ART's vision and current PI Objectives. If it aligns, it can be prioritized for the next PI, avoiding disruption to the current planning. This balances stakeholder input with the need to maintain focus and commitment during PI Planning.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Ask the Release Train Engineer (RTE) to decide whether to include the feature in the current PI.
Why it's wrong here
The RTE facilitates PI Planning but does not own prioritization; that is the Product Manager's responsibility. Delegating this decision to the RTE misaligns roles and may lead to inconsistent prioritization. The Product Manager should own the decision, considering stakeholder input and strategic alignment, rather than shifting accountability.
- ✗
Reject the feature outright because it was not in the original backlog.
Why it's wrong here
Outright rejection may alienate stakeholders and ignore potentially valuable input. The Product Manager should instead evaluate the feature's value and alignment with the ART's vision. A collaborative approach ensures that good ideas are not lost while protecting the current PI's scope. The decision should be based on prioritization, not simply on timing.
- ✗
Add the feature to the Program Backlog and ask the teams to estimate it during PI Planning.
Why it's wrong here
Adding a new feature just before PI Planning can disrupt the event and lead to overcommitment. The Product Manager should evaluate the request against existing priorities and capacity. Introducing unplanned work during PI Planning undermines the preparation process and may cause teams to miss their committed objectives. It's better to defer or negotiate.
- ✓
Evaluate the feature against the current PI Objectives and, if it aligns with the ART's vision, work with the stakeholder to prioritize it for the next PI.
Why this is correct
The Product Manager should assess the new feature against the ART's vision and current PI Objectives. If it aligns, it can be prioritized for the next PI, avoiding disruption to the current planning. This ensures strategic alignment and maintains the integrity of the PI Planning process. It also manages stakeholder expectations effectively.
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.