CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Backlog Management 1 — Questions and Answers
Question 1: Which of the following best describes a well-formed Product Backlog item ready for Sprint Planning?
- It is fully designed and includes detailed technical specifications approved by the development team lead
- It is small enough to complete within the Sprint, has clear acceptance criteria, and is understood by the Scrum Team (Correct answer)
- It has been approved by all stakeholders and signed off by the project manager
- It contains a complete implementation plan and estimated cost breakdown
Correct answer: It is small enough to complete within the Sprint, has clear acceptance criteria, and is understood by the Scrum Team
A Product Backlog item ready for Sprint Planning should be appropriately sized to fit within a Sprint, have clear acceptance criteria so the team knows when it's done, and be understood by the whole Scrum Team — not require sign-off from managers or full design specs upfront.
Question 2: A Product Owner discovers that two high-value Product Backlog items have a technical dependency — Item A must be completed before Item B. How should the Product Owner handle this?
- Remove Item B from the Product Backlog until Item A is released to production
- Order Item A above Item B in the Product Backlog so the Developers can address the dependency naturally (Correct answer)
- Escalate the dependency to the Scrum Master to resolve before the next Sprint
- Combine Items A and B into a single large backlog item to eliminate the dependency
Correct answer: Order Item A above Item B in the Product Backlog so the Developers can address the dependency naturally
The Product Owner manages dependencies through ordering. Placing Item A above Item B ensures the Developers work on the prerequisite first. Dependencies don't require removal of items or escalation to the Scrum Master — they are a normal input to backlog ordering decisions.
Question 3: How much time should a Scrum Team typically spend on Product Backlog refinement each Sprint?
- As much time as needed — refinement has no recommended time limit in Scrum
- No more than 10% of the Developers' capacity for the Sprint (Correct answer)
- Exactly one full day per Sprint, scheduled at the midpoint
- Refinement should only occur during Sprint Planning, not as a separate activity
Correct answer: No more than 10% of the Developers' capacity for the Sprint
The Scrum Guide suggests refinement should consume no more than 10% of the Developers' Sprint capacity. This keeps refinement lightweight while ensuring upcoming backlog items are sufficiently understood and estimated for future Sprints.
Question 4: A Product Owner is managing a backlog with 80 items. Which approach to detail and estimation is most consistent with Scrum principles?
- All 80 items should be fully detailed and estimated before any Sprint begins
- Items near the top of the backlog should be more detailed and refined; items lower down can remain coarser (Correct answer)
- Every item must have story points assigned by the Product Owner before Developer review
- Only items planned for the current Sprint need any detail; all others can remain as ideas
Correct answer: Items near the top of the backlog should be more detailed and refined; items lower down can remain coarser
Scrum embraces the concept of 'just enough, just in time.' Items near the top of the backlog (upcoming work) should be refined to a level ready for Sprint Planning, while lower-priority items can remain at a higher level of abstraction until they become relevant.
Question 5: The Developers inform the Product Owner that a significant amount of technical debt has accumulated and is slowing down feature delivery. What is the most appropriate action for the Product Owner?
- Reject the concern — technical debt is a Developer problem and should not appear in the Product Backlog
- Dedicate an entire Sprint exclusively to technical debt before allowing any feature work
- Add technical debt work as explicit Product Backlog items and order them relative to their impact on value delivery (Correct answer)
- Ask the Scrum Master to schedule a separate technical debt backlog outside of Scrum ceremonies
Correct answer: Add technical debt work as explicit Product Backlog items and order them relative to their impact on value delivery
Technical debt is legitimate work that affects the team's ability to deliver value. The Product Owner should represent this work as explicit backlog items and order them based on their impact on the product's long-term health and delivery speed — not ignore it or silo it outside the main backlog.
Question 6: At the end of a Sprint Review, several stakeholders suggest new ideas that the team finds exciting. What should the Product Owner do with these ideas?
- Immediately commit to delivering the ideas in the next Sprint to maintain stakeholder engagement
- Add the ideas to the Product Backlog for consideration, then order them based on value relative to existing items (Correct answer)
- Reject the ideas since they were not part of the original product vision agreed upon at project start
- Ask the Scrum Master to evaluate the ideas and decide which ones to include
Correct answer: Add the ideas to the Product Backlog for consideration, then order them based on value relative to existing items
The Sprint Review is designed to inspect the increment and adapt the Product Backlog based on feedback. New stakeholder ideas are captured in the backlog and then ordered by the Product Owner based on value — the Product Owner neither automatically commits to them nor dismisses them.
CSPO - Certified Scrum Product Owner® Certification Certified Scrum Product Owner®(CSPO) Product Backlog Management 1
Which of the following best describes a well-formed Product Backlog item ready for Sprint Planning?