CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Managing the Product Backlog 1 — Questions and Answers
Question 1: Which characteristic best describes a well-managed Product Backlog according to Scrum principles?
- It is locked at the start of each Sprint and cannot be changed until the Sprint Review
- It is detailed, estimated, emergent, and prioritized (DEEP) (Correct answer)
- It contains only items that have been approved by the Scrum Master
- It is maintained jointly by the Product Owner and the project manager
Correct answer: It is detailed, estimated, emergent, and prioritized (DEEP)
A healthy Product Backlog is DEEP: Detailed appropriately (higher-priority items have more detail), Estimated, Emergent (it evolves as new information surfaces), and Prioritized to reflect current business value. This ensures the team always has clear, actionable work ready.
Question 2: How frequently should Product Backlog refinement occur in Scrum?
- Once per Sprint, always on the first day
- As a continuous activity throughout the Sprint, consuming no more than 10% of the Development Team's capacity (Correct answer)
- Only before the Sprint Planning meeting begins
- Whenever the Product Owner decides it is necessary, without any time constraint
Correct answer: As a continuous activity throughout the Sprint, consuming no more than 10% of the Development Team's capacity
The Scrum Guide states that refinement is an ongoing activity, not a single event. The team should spend no more than 10% of its capacity on refinement so items are ready for upcoming Sprints without disrupting current Sprint work.
Question 3: A Product Owner discovers that a high-priority backlog item has grown so large it cannot be completed in a single Sprint. What is the best course of action?
- Move the item to the bottom of the backlog until the team has more capacity
- Keep the item as-is and plan for a multi-Sprint implementation without splitting it
- Collaborate with the Development Team to decompose the item into smaller, Sprint-sized stories that each deliver value (Correct answer)
- Ask the Scrum Master to add extra days to the Sprint to accommodate the large item
Correct answer: Collaborate with the Development Team to decompose the item into smaller, Sprint-sized stories that each deliver value
Items must fit within a Sprint to be actionable. The Product Owner should work with the Development Team to break the large item into smaller stories, each independently deliverable and valuable, ensuring flow and transparency.
Question 4: What is the recommended approach when multiple stakeholders disagree about the priority of items in the Product Backlog?
- Prioritize items alphabetically to avoid bias
- Let the Development Team vote on which items they prefer to work on
- The Product Owner listens to all input, weighs business value, risk, and dependencies, then makes the final ordering decision (Correct answer)
- Escalate the conflict to the Scrum Master, who breaks the tie
Correct answer: The Product Owner listens to all input, weighs business value, risk, and dependencies, then makes the final ordering decision
The Product Owner is solely accountable for ordering the Product Backlog. While stakeholder input is valuable and should be actively sought, the final prioritization decision rests with the Product Owner, who balances value, risk, and strategic alignment.
Question 5: Technical debt items identified by the Development Team should be handled in the Product Backlog by:
- Being tracked in a separate technical backlog maintained by the team lead, outside of Scrum
- Being added to the Product Backlog as explicit items that the Product Owner can prioritize alongside feature work (Correct answer)
- Being ignored until the debt causes visible defects for end users
- Being automatically placed at the top of every Sprint Backlog without Product Owner involvement
Correct answer: Being added to the Product Backlog as explicit items that the Product Owner can prioritize alongside feature work
All work, including technical debt, should be visible in a single Product Backlog. Making technical debt explicit allows the Product Owner to weigh it against feature work, balance short-term delivery with long-term sustainability, and make informed trade-offs.
Question 6: During Sprint Planning, the Development Team says several top-priority backlog items lack enough detail to begin work. What should have prevented this situation?
- The Scrum Master should have written the acceptance criteria before the meeting
- Ongoing Product Backlog refinement should have ensured near-term items were sufficiently detailed and met a Definition of Ready (Correct answer)
- The team should accept the items anyway and clarify details during the Sprint
- The Product Owner should reduce the scope of the Sprint Goal to only items that are fully specified
Correct answer: Ongoing Product Backlog refinement should have ensured near-term items were sufficiently detailed and met a Definition of Ready
Regular refinement ensures that items near the top of the backlog are broken down, estimated, and detailed enough for the team to commit to them. A Definition of Ready helps set the bar for when an item is truly sprint-ready, preventing planning bottlenecks.
CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Managing the Product Backlog 1
Which characteristic best describes a well-managed Product Backlog according to Scrum principles?