POPM Product Owner and Product Management Roles Practice Question

Answer analysis

Option-by-option breakdown

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

• ✗

  Drop the Feature from the PI and inform the Business Owners that the objective will not be met

  Why it's wrong here

  Dropping the Feature prematurely is a drastic action that abandons value that is already 60% delivered. The dependency may be resolvable through normal ART coordination. The Product Manager should first attempt to unblock the work before recommending descoping to Business Owners, who rely on the PI Objectives.

• ✗

  Reassign the Feature to a different team on the same train that has more capacity

  Why it's wrong here

  Reassigning a partially completed Feature mid-PI ignores the dependency that is actually blocking progress. The new team would inherit the same external blocker and likely lack the context and skills. This action does not resolve the cross-ART dependency and risks further delay and rework, so it is not the best first step.

• ✗

  Ask the team to work overtime to complete the Feature without addressing the dependency

  Why it's wrong here

  Working overtime cannot overcome an external dependency that the team does not control. This approach risks burnout, quality problems, and still leaves the Feature blocked. It also violates Lean-Agile principles of sustainable pace. The root cause must be addressed through dependency management, not by adding hours.

• ✓

  Escalate the dependency to the Release Train Engineer and work with the other ART to resolve it at the ART Sync

  Why this is correct

  The Release Train Engineer owns the ART Sync and dependency management across teams. Escalating the blocked dependency there allows the ART to remove the impediment quickly. The Product Manager's role is to ensure value delivery, and using the established ART Sync mechanism is the fastest, most appropriate first action to protect the PI Objectives.