PSPO Value-Based Prioritization Techniques 2 — Questions and Answers
Question 1: Which technique helps Product Owners visualize user journeys and organize Product Backlog items by user activities across a timeline?
- Burndown Charts
- Affinity Mapping
- User Story Mapping (Correct answer)
- Velocity Charts
Correct answer: User Story Mapping
User Story Mapping arranges stories horizontally by user activity flow and vertically by priority, making it easy to see slices of value for incremental releases.
Question 2: In a 2×2 Value vs. Effort priority matrix, how should items with HIGH value and LOW effort be treated?
- Deprioritized until capacity allows
- Scheduled as quick wins and done first (Correct answer)
- Delayed until high-effort items are finished
- Delegated to other teams
Correct answer: Scheduled as quick wins and done first
High value, low effort items maximize return on investment and should be prioritized first as they deliver the most value for the least cost.
Question 3: Which prioritization technique starts with the desired business outcome and maps backwards through user impacts to the features and deliverables needed?
- MoSCoW
- Weighted Shortest Job First
- User Story Mapping
- Impact Mapping (Correct answer)
Correct answer: Impact Mapping
Impact Mapping uses a 'Why-Who-How-What' structure starting from the business goal and working backward to identify which features actually support that goal.
Question 4: When a Product Owner applies 'Opportunity Cost' in backlog prioritization, they are accounting for:
- The cost of hiring additional developers
- The expense of running Scrum ceremonies each sprint
- The value foregone by choosing one backlog item over another (Correct answer)
- The infrastructure cost of the chosen technical solution
Correct answer: The value foregone by choosing one backlog item over another
Opportunity cost in prioritization represents the value of the best alternative item not chosen, ensuring the Product Owner makes economically conscious ordering decisions.
Question 5: In the Kano Model, 'Performance features' (one-dimensional quality) are best described as features that:
- Surprise and delight customers when unexpectedly present
- Are technically required but entirely invisible to the user
- Generate customer satisfaction proportional to their quantity and quality (Correct answer)
- Customers do not notice until they are completely absent
Correct answer: Generate customer satisfaction proportional to their quantity and quality
Performance features follow a linear satisfaction curve — more of them means more satisfaction, and less means less satisfaction, making them directly tied to competitive differentiation.
Question 6: What is the primary purpose of relative estimation techniques like Planning Poker when used to support prioritization?
- To assign precise hour estimates to each backlog item
- To determine each team member's daily work capacity
- To calculate the exact sprint burn rate
- To rank items against each other rather than applying absolute measures (Correct answer)
Correct answer: To rank items against each other rather than applying absolute measures
Relative estimation leverages team consensus to compare items to one another, which is faster and more accurate than absolute hour estimation for prioritization purposes.
Question 7: A Product Owner wants to reduce risk while delivering early value. Which backlog ordering strategy best achieves both goals simultaneously?
- Prioritize high-value, high-risk items early to learn and adapt sooner (Correct answer)
- Always prioritize the easiest items regardless of their business value
- Let the development team decide backlog order based on technical convenience
- Order all items by stakeholder seniority of the requester
Correct answer: Prioritize high-value, high-risk items early to learn and adapt sooner
Tackling high-value, high-risk items early surfaces unknowns when the team still has time to adapt, combining early value delivery with empirical risk management.
Which technique helps Product Owners visualize user journeys and organize Product Backlog items by user activities across a timeline?