APM Product Backlog Management and Prioritization 3 — Questions and Answers
Question 1: A product owner is using the Kano model. Which category describes features that cause dissatisfaction if absent but provide no delight when present?
- Excitement (delighters)
- Performance (linear)
- Basic (must-be) (Correct answer)
- Indifferent
Correct answer: Basic (must-be)
Basic/must-be features are expected by users — their absence causes dissatisfaction, but their presence is simply taken for granted and doesn't increase satisfaction.
Question 2: How does 'continuous refinement' differ from a dedicated backlog grooming session?
- Continuous refinement happens daily in small increments rather than in a single scheduled meeting (Correct answer)
- Continuous refinement is performed only by the Scrum Master
- Continuous refinement eliminates the need for sprint planning
- Continuous refinement focuses only on technical debt
Correct answer: Continuous refinement happens daily in small increments rather than in a single scheduled meeting
Continuous refinement distributes grooming activities throughout the sprint in short, frequent interactions, reducing the overhead of a single long grooming meeting.
Question 3: In SAFe, what is the purpose of the Program Backlog?
- To store all individual user stories for a single Agile team
- To hold features and enablers prioritized for delivery by an Agile Release Train (Correct answer)
- To track defects found during system testing
- To list all ideas rejected by the product manager
Correct answer: To hold features and enablers prioritized for delivery by an Agile Release Train
The SAFe Program Backlog contains features and enablers that are prioritized using WSJF for implementation by the Agile Release Train.
Question 4: A product owner wants to ensure the team understands 'why' behind each backlog item. Which practice achieves this BEST?
- Writing technical implementation notes for each item
- Adding outcome-focused user story narratives with clear business value (Correct answer)
- Assigning story points before refinement
- Color-coding items by priority tier
Correct answer: Adding outcome-focused user story narratives with clear business value
User stories written in the format 'As a [user], I want [feature] so that [benefit]' communicate the 'why' and keep the team focused on delivering value.
Question 5: What risk does a product owner face when prioritizing ONLY by stakeholder requests?
- The backlog becomes too small
- High-value customer needs may be overlooked in favor of vocal internal stakeholders (Correct answer)
- Sprint velocity increases too quickly
- The Definition of Done becomes unclear
Correct answer: High-value customer needs may be overlooked in favor of vocal internal stakeholders
Stakeholder-driven prioritization without customer data tends to favor loudest voices over actual user needs, leading to low-value features consuming team capacity.
Question 6: Which metric BEST indicates whether the product backlog is well-maintained?
- The total number of items in the backlog
- The percentage of items that are estimated, refined, and actionable at any given time (Correct answer)
- The number of sprints planned in advance
- The ratio of bugs to user stories
Correct answer: The percentage of items that are estimated, refined, and actionable at any given time
A healthy backlog has a sufficient number of 'ready' items at the top and decreasing detail toward the bottom, ensuring the team can always plan the next sprint.
Question 7: When should a product owner remove an item from the product backlog?
- After every sprint regardless of value
- When the item's cost to implement clearly outweighs its expected value or it becomes obsolete (Correct answer)
- Only after getting written approval from all stakeholders
- When the item has been in the backlog for more than 30 days
Correct answer: When the item's cost to implement clearly outweighs its expected value or it becomes obsolete
Items should be removed when they no longer add value, the opportunity has passed, or the cost-benefit analysis no longer justifies implementation.
A product owner is using the Kano model.
Which category describes features that cause dissatisfaction if absent but provide no delight when present?