Certified Scrum Product Owner®(CSPO) Managing the Product Backlog Questions and Answers Flashcards
6 cards from real CSPO practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Certified Scrum Product Owner®(CSPO) Managing the Product Backlog Questions and Answers flashcards as text
What is the primary purpose of Product Backlog refinement?
Answer: To add detail, estimates, and order to Product Backlog items
Refinement is the ongoing activity of adding detail, estimates, and order to items in the Product Backlog so they are ready for selection in Sprint Planning.
Who is responsible for ordering the Product Backlog?
Answer: The Product Owner
The Product Owner is the sole person responsible for ordering the Product Backlog to maximize the value delivered by the Scrum Team.
A stakeholder requests a feature that conflicts with the current product strategy. What should the Product Owner do?
Answer: Evaluate the request against the Product Goal and discuss trade-offs with the stakeholder
The Product Owner should evaluate all requests against the Product Goal and transparently discuss trade-offs with stakeholders before making ordering decisions.
Which technique helps a Product Owner split large Product Backlog items into smaller ones?
Answer: INVEST criteria
The INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) guide Product Owners in creating well-sized backlog items.
What happens to Product Backlog items that are not selected during Sprint Planning?
Answer: They remain in the Product Backlog for future consideration and re-ordering
Unselected items remain in the Product Backlog and may be refined, re-ordered, or selected in future Sprints based on evolving priorities.
How should a Product Owner handle dependencies between Product Backlog items?
Answer: Order dependent items to minimize risk and coordinate with affected teams
The Product Owner should order dependent items thoughtfully to reduce risk and collaborate with teams to manage cross-team dependencies effectively.