Sprint Planning and Collaboration Flashcards

Why is it important for the Product Owner to attend the Sprint Review?

Answer: To inspect the Increment and adapt the Product Backlog based on outcomes and stakeholder feedback

The Product Owner uses the Sprint Review to inspect the Increment, gather stakeholder feedback, and make informed backlog adaptations for the next Sprint.

During Sprint Planning, how should the Product Owner handle conflicting stakeholder priorities?

Answer: Present a single prioritized backlog reflecting their best judgment of value

The Product Owner is accountable for ordering the backlog and must present a single prioritized list, having already resolved conflicts with stakeholders beforehand.

What is the relationship between the Sprint Goal and the Product Goal?

Answer: The Sprint Goal is a step toward achieving the longer-term Product Goal

Each Sprint Goal should be a coherent step toward the Product Goal, ensuring Sprint work aligns with the longer-term product vision.

Who is responsible for ensuring that Product Backlog items are refined enough for Sprint Planning?

Answer: The Product Owner, with Developers' input during refinement

The Product Owner is accountable for backlog readiness but works collaboratively with Developers during refinement sessions to ensure items are clear and estimated.

How should a Product Owner communicate urgency for a particular feature to Developers?

Answer: By ordering it high in the Product Backlog and explaining the business value during Planning

The Product Owner communicates urgency through backlog ordering and explaining business context, allowing Developers to understand and respond appropriately.

What should a Product Owner do if the Scrum Team consistently fails to meet the Sprint Goal?

Answer: Investigate root causes in the Sprint Retrospective and adapt processes accordingly

Consistently missing Sprint Goals signals systemic issues that should be surfaced and addressed collaboratively in the Sprint Retrospective.