Product Backlog Management and Prioritization Flashcards
7 cards from real APM practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Product Backlog Management and Prioritization flashcards as text
A product owner is using the Kano model. Which category describes features that cause dissatisfaction if absent but provide no delight when present?
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.
How does 'continuous refinement' differ from a dedicated backlog grooming session?
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.
In SAFe, what is the purpose of the Program Backlog?
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.
A product owner wants to ensure the team understands 'why' behind each backlog item. Which practice achieves this BEST?
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.
What risk does a product owner face when prioritizing ONLY by stakeholder requests?
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.
Which metric BEST indicates whether the product backlog is well-maintained?
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.
When should a product owner remove an item from the product backlog?
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.