CSPO Managing the Product Backlog 5 â Questions and Answers
Question 1: Which factor should a Product Owner consider LEAST when ordering Product Backlog items?
- Business value delivered
- Technical dependencies between items
- The personal preference of the loudest stakeholder (Correct answer)
- Risk and uncertainty
Correct answer: The personal preference of the loudest stakeholder
Stakeholder preference alone â especially when it comes from volume or politics rather than value â should not drive backlog ordering decisions.
Question 2: How does the Product Owner collaborate with the Development Team during backlog refinement?
- The Product Owner presents items and the team passively listens
- The Product Owner and team jointly clarify, estimate, and decompose items together (Correct answer)
- The Development Team refines the backlog independently and presents it to the Product Owner
- Refinement is a solo activity for the Product Owner only
Correct answer: The Product Owner and team jointly clarify, estimate, and decompose items together
Refinement is a collaborative activity where the Product Owner and Development Team work together to clarify requirements and update estimates.
Question 3: A Product Owner wants to use story maps to manage the Product Backlog. Is this compatible with Scrum?
- No, Scrum mandates a flat, ordered list format
- Yes, story mapping is a complementary technique that can help visualize and organize the backlog (Correct answer)
- No, only the Scrum Master may introduce visualization tools
- Yes, but only for projects with fewer than 50 backlog items
Correct answer: Yes, story mapping is a complementary technique that can help visualize and organize the backlog
Story mapping and other complementary techniques are entirely compatible with Scrum and can help teams understand scope and flow.
Question 4: What is the MOST effective way to communicate backlog priorities to stakeholders who are not in Sprint Planning?
- Send a weekly email listing the top 10 items
- Make the Product Backlog transparent and accessible, and hold regular stakeholder reviews (Correct answer)
- Restrict backlog visibility to protect the team from interference
- Share only the Sprint Backlog after each planning event
Correct answer: Make the Product Backlog transparent and accessible, and hold regular stakeholder reviews
Transparency and regular stakeholder engagement â such as Sprint Reviews â keep stakeholders informed and aligned without disrupting the team.
Question 5: The Development Team consistently underestimates items during refinement, causing Sprint goals to be missed. What should the Product Owner do?
- Reduce the Sprint length to decrease planning risk
- Work with the team to inspect and improve the estimation process and add buffer items (Correct answer)
- Override the team's estimates with their own
- Remove estimation from the refinement process entirely
Correct answer: Work with the team to inspect and improve the estimation process and add buffer items
Persistent estimation misses are a signal to inspect and adapt the refinement and estimation approach, ideally surfaced in the Sprint Retrospective.
Question 6: When should a Product Owner consider removing an item from the Product Backlog?
- After every Sprint to keep the backlog short
- When the item no longer provides value relative to other items or the need it addressed has changed (Correct answer)
- Only after stakeholder approval for each removal
- Never â all items should remain for historical traceability
Correct answer: When the item no longer provides value relative to other items or the need it addressed has changed
Items that have lost their value or relevance should be removed to keep the backlog focused and manageable.
Question 7: A Product Owner is asked to maintain two separate backlogs for two different stakeholder groups within one product. What is the BEST response?
- Maintain two separate backlogs to satisfy each stakeholder group
- Combine all items into a single Product Backlog ordered by overall value (Correct answer)
- Ask the Scrum Master to manage the second backlog
- Create a separate Scrum team for each stakeholder group
Correct answer: Combine all items into a single Product Backlog ordered by overall value
A single product has a single Product Backlog; the Product Owner integrates all stakeholder needs into one prioritized list.
Which factor should a Product Owner consider LEAST when ordering Product Backlog items?