Product Backlog Management 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 flashcards as text
A Product Owner discovers that a backlog item has been sitting unprioritized for six sprints. What is the BEST course of action?
Answer: Discuss it with stakeholders to determine if it still adds value
Old backlog items should be reviewed with stakeholders to verify their continued relevance and value before any prioritization decision.
Which technique helps a Product Owner group related backlog items to visualize the full scope of a feature?
Answer: Story mapping
Story mapping arranges user stories along a timeline of user activities, helping teams visualize the full product scope and identify gaps.
When writing acceptance criteria for a Product Backlog Item, the criteria should primarily be written from whose perspective?
Answer: The end user or business stakeholder
Acceptance criteria define the conditions that must be met from the user or stakeholder perspective to consider the story done.
A team consistently completes only 60% of their sprint commitment. How should the Product Owner address this in backlog management?
Answer: Collaborate with the team to better size items and set realistic commitments
Persistent under-delivery signals that items may be poorly understood or oversized, requiring collaborative refinement to improve accuracy.
What is the PRIMARY purpose of backlog grooming sessions conducted before a sprint?
Answer: To ensure upcoming items are well-understood, estimated, and prioritized
Backlog refinement ensures the top items are ready—detailed, estimated, and ordered—so the team can confidently plan the next sprint.
A stakeholder requests that a low-priority backlog item be completed within two sprints despite higher-priority work. What should the Product Owner do?
Answer: Explain the trade-offs and negotiate based on business value and cost
The Product Owner must transparently communicate trade-offs so stakeholders understand the impact of reprioritizing on higher-value work.
Which of the following BEST describes an 'epic' in the context of a product backlog?
Answer: A large user story that needs to be broken into smaller stories before it can be developed
An epic is a large body of work that is too big to fit in a single sprint and must be decomposed into smaller, actionable user stories.