CSPO Product Backlog Management 5 — Questions and Answers
Question 1: Which of the following is NOT a valid reason to reorder the Product Backlog?
- A competitor released a similar feature earlier than expected
- A senior developer prefers to work on the technically interesting item first (Correct answer)
- New user research reveals a higher-value opportunity
- A regulatory deadline has moved up
Correct answer: A senior developer prefers to work on the technically interesting item first
Backlog ordering is driven by business value, risk, and strategic goals—not by developer preferences or technical interests.
Question 2: In Scrum, who may add items to the Product Backlog?
- Only the Product Owner
- Only the Development Team during Sprint Planning
- Anyone, but the Product Owner decides the order and what is included (Correct answer)
- Only stakeholders who attend Sprint Reviews
Correct answer: Anyone, but the Product Owner decides the order and what is included
Anyone may submit items to the Product Backlog, but the Product Owner is solely accountable for ordering it and deciding which items are included.
Question 3: A Product Owner is told by the Scrum Master that the team spends more than 10% of each Sprint on refinement. What does this suggest?
- The team is over-investing in refinement and should stop immediately
- The backlog may have too many ill-defined items requiring excessive clarification (Correct answer)
- Refinement sessions should be replaced with written specifications
- The Scrum Master is micromanaging the team's time
Correct answer: The backlog may have too many ill-defined items requiring excessive clarification
While 10% is a rough guideline, consistently exceeding it may indicate systemic backlog clarity issues that the Product Owner should address proactively.
Question 4: What is the MAIN difference between a Product Backlog and a Sprint Backlog?
- The Product Backlog lists all known work for the product; the Sprint Backlog contains work selected for a single Sprint (Correct answer)
- The Sprint Backlog is owned by the Product Owner; the Product Backlog is owned by the team
- Product Backlog items must be estimated; Sprint Backlog items do not need estimates
- The Sprint Backlog is a subset of the Product Backlog filtered by technical complexity
Correct answer: The Product Backlog lists all known work for the product; the Sprint Backlog contains work selected for a single Sprint
The Product Backlog is the comprehensive ordered list of everything that might be needed in the product, while the Sprint Backlog contains only the items selected for the current Sprint.
Question 5: A Product Owner notices that the Development Team consistently underestimates Product Backlog items during refinement. What is the BEST response?
- Override the team's estimates with more accurate management estimates
- Collaborate with the team to review past items and improve estimation accuracy over time (Correct answer)
- Break items into smaller pieces until estimates become more reliable
- Stop estimating and use a flow-based approach instead
Correct answer: Collaborate with the team to review past items and improve estimation accuracy over time
Reviewing past estimates against actual outcomes helps the team calibrate their judgment and improve accuracy through empirical learning.
Question 6: A Product Owner is asked to provide a roadmap to stakeholders. How should the roadmap relate to the Product Backlog?
- The roadmap replaces the Product Backlog for strategic planning purposes
- The roadmap reflects the intended direction and high-level goals, while the Product Backlog details the near-term work to achieve them (Correct answer)
- The roadmap must match the Product Backlog item-by-item with fixed delivery dates
- Roadmaps are a Waterfall artifact and should not be used with Scrum
Correct answer: The roadmap reflects the intended direction and high-level goals, while the Product Backlog details the near-term work to achieve them
A roadmap communicates strategic direction and high-level intent, while the Product Backlog provides the actionable detail for near-term work toward that direction.
Question 7: A Product Owner wants to use story mapping to improve backlog organization. What is the PRIMARY benefit of story mapping?
- It replaces the need for Sprint Planning by scheduling all work in advance
- It creates a visual narrative of user journeys that helps identify gaps and prioritize holistically (Correct answer)
- It automatically estimates story points for each backlog item
- It enforces technical dependencies between backlog items
Correct answer: It creates a visual narrative of user journeys that helps identify gaps and prioritize holistically
Story mapping arranges backlog items along a user journey backbone, making gaps visible and helping teams release the smallest coherent slice of value.
CSPO Product Backlog Management 5
Which of the following is NOT a valid reason to reorder the Product Backlog?