CSPO Scrum Product Owner 3 — Questions and Answers
Question 1: What distinguishes an Epic from a User Story in the context of Product Backlog management?
- An Epic is a completed story while a User Story is in progress
- An Epic is a large backlog item that can be broken down into smaller User Stories (Correct answer)
- Epics are managed by the Scrum Master, not the Product Owner
- User Stories are always larger than Epics
Correct answer: An Epic is a large backlog item that can be broken down into smaller User Stories
Epics are large, high-level backlog items that are decomposed into smaller, more actionable User Stories as they approach implementation.
Question 2: How should a Product Owner handle a situation where two stakeholders have conflicting priorities?
- Let the stakeholders fight it out among themselves
- Facilitate a conversation, weigh business value and strategy, and make a final prioritization decision (Correct answer)
- Always side with the higher-ranking stakeholder
- Escalate to the Scrum Master to resolve
Correct answer: Facilitate a conversation, weigh business value and strategy, and make a final prioritization decision
The Product Owner is accountable for prioritization decisions and must balance stakeholder input against the overall product strategy.
Question 3: Which of the following best describes 'Value' in the context of a Product Owner's decisions?
- The monetary cost of developing a feature
- The benefit delivered to customers, users, or the business relative to the effort invested (Correct answer)
- The number of story points completed in a Sprint
- The satisfaction score given by the Development Team
Correct answer: The benefit delivered to customers, users, or the business relative to the effort invested
Value encompasses customer benefit, business outcomes, and strategic alignment—not just cost or team throughput.
Question 4: The Scrum Guide states the Product Owner is accountable for maximizing the value of the product. Who is responsible for how this is achieved?
- The Scrum Master
- It varies greatly depending on the organization, team, and individual (Correct answer)
- Always the CEO
- The Development Team exclusively
Correct answer: It varies greatly depending on the organization, team, and individual
The Scrum Guide acknowledges that how the Product Owner maximizes value varies greatly across organizations and contexts.
Question 5: A Product Owner wants to improve stakeholder engagement during Sprint Reviews. What is the most effective approach?
- Send written summaries instead of holding meetings
- Invite relevant stakeholders, demonstrate working software, and actively solicit feedback (Correct answer)
- Only invite the most senior executives
- Present a slideshow of completed tasks
Correct answer: Invite relevant stakeholders, demonstrate working software, and actively solicit feedback
Sprint Reviews are most effective when key stakeholders inspect working software and provide actionable feedback to shape future development.
Question 6: What should a Product Owner do if the Development Team says a Product Backlog item cannot be completed within a single Sprint?
- Force the team to complete it anyway
- Work with the team to split the item into smaller, Sprint-sized pieces (Correct answer)
- Remove the item from the Product Backlog permanently
- Have the Scrum Master break it down independently
Correct answer: Work with the team to split the item into smaller, Sprint-sized pieces
Splitting large items into smaller, deliverable pieces is a core practice of Product Backlog refinement and ensures each Sprint can produce a valuable Increment.
Question 7: In Scrum, who determines the Definition of Done?
- The Product Owner alone
- The Scrum Team, and if not in place, the Development Team with organizational standards as a minimum (Correct answer)
- The Scrum Master alone
- External auditors
Correct answer: The Scrum Team, and if not in place, the Development Team with organizational standards as a minimum
The Definition of Done is created by the Scrum Team, and if organizational standards exist, they form the minimum baseline.
What distinguishes an Epic from a User Story in the context of Product Backlog management?