POPM PI Planning Preparation Practice Question
During PI Planning preparation, a Product Manager is refining the Program Backlog to ensure features are ready for the upcoming PI. The PM wants to apply Weighted Shortest Job First (WSJF) to prioritize features. Which action best supports effective WSJF calculation?
⚠ Common exam trap
The trap here is assuming WSJF can be done with a single priority rank or by sorting on story points, rather than calculating Cost of Delay divided by Job Size from relative estimates.
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
✓
Estimate the Cost of Delay components and job size for each feature using relative estimation.
WSJF ranks features by dividing Cost of Delay by Job Size. Cost of Delay comprises user-business value, time criticality, and risk reduction/opportunity enablement. Each component must be estimated relatively to derive a WSJF score. This economic prioritization helps the Product Manager sequence the Program Backlog so that the ART can plan the highest-value work first 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.
- ✗
Assign a single priority rank to each feature based on stakeholder input.
Why it's wrong here
Assigning a single priority rank bypasses the relative scoring that WSJF requires. WSJF needs separate estimates for user-business value, time criticality, risk reduction/opportunity enablement, and job size. A single rank collapses these dimensions and cannot produce the Cost of Delay divided by Job Size ratio, leading to prioritization that ignores economic trade-offs.
- ✓
Estimate the Cost of Delay components and job size for each feature using relative estimation.
Why this is correct
WSJF is calculated as Cost of Delay divided by Job Size. To compute Cost of Delay, the team must estimate user-business value, time criticality, and risk reduction/opportunity enablement, typically using relative scales like modified Fibonacci. Job size is also estimated relatively. This approach ensures prioritization reflects economic value and effort, enabling the PM to sequence features effectively for PI Planning.
- ✗
Prioritize features solely by the number of dependencies identified on the Program Board.
Why it's wrong here
Dependencies are important for planning but are not a WSJF input. WSJF focuses on economic value and job size. Prioritizing by dependency count would ignore value and urgency, potentially delaying high-value features. Dependencies are addressed during PI Planning when teams coordinate, but they should not replace WSJF for backlog prioritization.
- ✗
Use the team's velocity to assign story points to each feature, then sort by story points.
Why it's wrong here
Sorting by story points would prioritize small features regardless of their value or urgency. WSJF explicitly divides Cost of Delay by Job Size, so a small feature with low value may still rank lower than a larger feature with high value and urgency. Using velocity to size features is also inappropriate because features span multiple teams and are not estimated in story points.
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.