Courseiva
PI Planning Preparation →mediumMultiple Choice

POPM PI Planning Preparation Practice Question

During PI Planning, a team expresses concern that they cannot fulfill a high-priority feature. What should the Product Manager do first?

⚠ Common exam trap

Candidates often incorrectly choose options like arbitrarily increasing team velocity or rejecting the feature entirely, forgetting that Agile emphasizes collaborative scope negotiation.

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

✓

Discuss scope trade-offs to define a smaller, viable increment.

The Product Manager must immediately engage in a collaborative trade-off discussion. The goal is to understand the constraints (technical, capacity, or dependency) and negotiate scope. By working together, the PM and the team can find a way to deliver a 'Minimum Viable Feature' or adjust the scope to maintain the program's overall objectives without sacrificing the integrity of the release plan.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • ✗

    Insist the team makes the feature a priority at all costs.

    Why it's wrong here

    Demanding compliance disregards the team's professional assessment of their capacity and capability. This creates a morale issue and increases the risk of quality failure. The PM should focus on collaboration and negotiation rather than top-down mandates, which are antithetical to the principles of Agile and team autonomy.

  • ✗

    Remove the feature from the PI and move it to the next one.

    Why it's wrong here

    Moving the feature immediately is a reactive, rather than a collaborative, approach. It might not be necessary if the scope can be adjusted or if help can be provided. Engaging in a discussion first allows for potential solutions that keep the value delivery on track for the current PI.

  • ✓

    Discuss scope trade-offs to define a smaller, viable increment.

    Why this is correct

    Collaborating on scope allows the team to commit to what is actually possible. By defining a 'Minimum Viable Feature,' the PM can still deliver value within the PI, maintaining the program's momentum while respecting the team's capacity constraints and ensuring that the final output is achievable and high-quality.

  • ✗

    Escalate the issue to the Release Train Engineer immediately.

    Why it's wrong here

    Escalation should be a last resort after attempts at collaboration have failed. Bringing the RTE in immediately bypasses the team's ability to self-solve and negotiate. It creates an adversarial environment that hinders the collaborative spirit required for successful PI Planning and future team-based problem solving.

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 →

How Courseiva writes practice questions · Editorial policy

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.