Product Backlog Management Flashcards
7 cards from real CAE 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 on a scaled agile team must align their product backlog with a Program Increment (PI). What is the BEST approach?
Answer: Ensure backlog items map to PI objectives and are synchronized with other teams
In scaled agile, a team's backlog must align with PI objectives and cross-team dependencies to enable coordinated delivery.
Which statement about technical debt items in the product backlog is MOST accurate?
Answer: Technical debt items compete with feature work and should be visible in the backlog
Making technical debt visible in the backlog allows the Product Owner and team to make informed trade-off decisions about when to address it.
A Product Owner wants to validate assumptions before committing development resources to a large backlog feature. What technique is MOST appropriate?
Answer: Create a spike or prototype to gather evidence before full development
Spikes are time-boxed research efforts that reduce uncertainty and validate assumptions before the team invests in full development.
In a scenario where a product backlog has 200+ items, what strategy helps the Product Owner maintain focus?
Answer: Focus detailed attention on the top 10-15 items; keep lower items intentionally vague
The iceberg principle: only items near the top need detailed refinement; distant items can remain at a higher level of abstraction.
A regulatory compliance requirement must be met before launch. How should this be reflected in the product backlog?
Answer: Add it as a backlog item with high priority and clear acceptance criteria tied to the regulation
Compliance requirements are legitimate backlog items that must be prioritized, estimated, and completed like any other feature.
What is the key difference between a product backlog item (PBI) and a task in the sprint backlog?
Answer: PBIs represent customer-facing value; tasks are the technical steps to deliver that value
PBIs describe what the customer needs (value-level), while sprint tasks describe the specific technical work required to build the PBI.
A newly formed agile team asks how many items should be in their initial product backlog. The best answer is:
Answer: Enough to fill the first two to three sprints in detail, with higher-level items beyond that
A healthy initial backlog has just enough detail for near-term sprints while keeping future items at a higher level to allow for emerging understanding.