CSPO Product Backlog Management 2 — Questions and Answers
Question 1: A Product Owner wants to ensure the Product Backlog is always ready for Sprint Planning. What does this 'ready' state typically mean?
- All items are estimated in story points
- The top items are refined enough for the team to select and execute in a Sprint (Correct answer)
- The entire backlog has been reviewed by stakeholders
- All items have been assigned to specific developers
Correct answer: The top items are refined enough for the team to select and execute in a Sprint
A 'ready' Product Backlog means the top items are sufficiently detailed, estimated, and understood so the team can confidently select them during Sprint Planning.
Question 2: Which technique is MOST effective when the Product Owner needs to split a large Product Backlog item into smaller stories?
- Divide it by architectural layers (front-end, back-end, database)
- Split by workflow steps, business rules, or acceptance criteria variations (Correct answer)
- Assign each piece to a different team member
- Defer splitting until the Sprint it will be worked on
Correct answer: Split by workflow steps, business rules, or acceptance criteria variations
Splitting by workflow steps, business rules, or acceptance criteria variations produces independently valuable vertical slices rather than technical layers.
Question 3: A stakeholder insists that their feature request be placed at the top of the Product Backlog. What is the Product Owner's BEST response?
- Immediately reprioritize to satisfy the stakeholder
- Evaluate the request against product goals and transparently explain the prioritization decision (Correct answer)
- Escalate the conflict to the Scrum Master
- Add the item but do not commit to when it will be delivered
Correct answer: Evaluate the request against product goals and transparently explain the prioritization decision
The Product Owner is accountable for ordering the backlog to maximize value, and should evaluate any request against product goals while explaining the rationale transparently.
Question 4: What is the primary purpose of Product Backlog Refinement in Scrum?
- To finalize sprint commitments before Sprint Planning
- To add detail, estimates, and order to Product Backlog items (Correct answer)
- To review completed work from the previous Sprint
- To assign backlog items to Development Team members
Correct answer: To add detail, estimates, and order to Product Backlog items
Refinement is the ongoing act of adding detail, estimates, and order to Product Backlog items so they are better understood by the Scrum Team.
Question 5: The Scrum Guide states that the Product Backlog is never complete. What does this mean for a Product Owner?
- The team will never finish all the work
- The backlog evolves as the product, market, and stakeholder needs change over time (Correct answer)
- The Product Owner has failed to scope the product properly
- Items should never be removed from the backlog
Correct answer: The backlog evolves as the product, market, and stakeholder needs change over time
An ever-evolving backlog reflects the dynamic nature of product development—new insights, market shifts, and stakeholder feedback continuously shape what is needed.
Question 6: A Product Owner is using the DEEP acronym to describe a healthy Product Backlog. What does DEEP stand for?
- Detailed, Estimated, Emergent, Prioritized
- Defined, Executable, Emerging, Planned
- Detailed appropriately, Estimated, Emergent, Prioritized (Correct answer)
- Dynamic, Evolving, Executable, Prioritized
Correct answer: Detailed appropriately, Estimated, Emergent, Prioritized
DEEP stands for Detailed appropriately (near-term items have more detail), Estimated, Emergent (it evolves), and Prioritized.
Question 7: When multiple Scrum Teams work on the same product, how should the Product Backlog be managed?
- Each team maintains its own separate Product Backlog
- There is one Product Backlog for the product, managed by one Product Owner (Correct answer)
- The Scrum Masters collectively manage a shared backlog
- Teams vote on backlog ordering during a joint Sprint Planning
Correct answer: There is one Product Backlog for the product, managed by one Product Owner
Regardless of how many Scrum Teams work on a product, there is only one Product Backlog and one Product Owner responsible for it.
CSPO Product Backlog Management 2
A Product Owner wants to ensure the Product Backlog is always ready for Sprint Planning.
What does this 'ready' state typically mean?