POPM PI Planning Preparation Practice Question
As a PM, you have several features with similar business value. Which criterion should be used to differentiate their priority in the Program Backlog?
⚠ Common exam trap
Candidates often try to guess which feature is 'more important' without a data-driven approach. They forget that WSJF uses job size to break ties between equal values.
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
✓
The estimated job size.
When business value is equal, the 'Job Size' (specifically duration or effort) becomes the deciding factor in the WSJF calculation. By prioritizing the smaller job, the team can realize the value sooner. This is critical because it improves flow, reduces the number of work items in progress, and accelerates the delivery of value to the customer, which is the core objective of the PI Planning preparation process.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The number of stakeholders requesting the feature.
Why it's wrong here
Popularity or the number of stakeholders does not equate to objective business value or urgency. Relying on stakeholder quantity can lead to prioritizing 'loudest' requests rather than those that truly drive the best economic outcomes for the organization. Data-driven prioritization through WSJF should always supersede stakeholder influence.
- ✓
The estimated job size.
Why this is correct
According to WSJF, when business value is equivalent, the feature with the smaller job size will have a higher priority score. This ensures faster time-to-market for that specific value, reduces complexity, and helps maintain a steady flow of finished features throughout the upcoming PI's iterations.
- ✗
The technical difficulty of the implementation.
Why it's wrong here
Prioritizing by difficulty can lead to 'gold-plating' or focusing on technically interesting tasks that lack market value. While technical feasibility is important, it should not dictate priority order. The goal is to maximize business outcomes, and difficult tasks should be addressed when they provide the highest relative value.
- ✗
The date the request was first submitted.
Why it's wrong here
First-in-first-out is an ineffective prioritization strategy because it ignores the changing market landscape and the time-sensitivity of features. Features that were requested long ago may no longer be relevant. Prioritization must be dynamic, reflecting current business strategy and the cost of delay, rather than historical chronological order.
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.