Sprint Planning and Goals Flashcards

A team finishes its Sprint Goal early with capacity left. What should they do?

Answer: Collaborate with the Product Owner to pull in additional valuable work

The team can work with the Product Owner to add suitable additional Product Backlog items within the Sprint.

During Sprint Planning the team realizes they cannot complete a selected item. What is the best response?

Answer: Renegotiate scope with the Product Owner to protect the Sprint Goal

Scope is renegotiated with the Product Owner so the Sprint Goal remains achievable.

What primarily informs how much work the Developers forecast for the Sprint?

Answer: Past performance, upcoming capacity, and Definition of Done

Developers use past performance, expected capacity, and their Definition of Done to forecast the Sprint's work.

If a Sprint Goal becomes obsolete mid-Sprint, who can cancel the Sprint?

Answer: The Product Owner

Only the Product Owner has the authority to cancel a Sprint.

Why is a single Sprint Goal preferred over multiple unrelated goals in one Sprint?

Answer: It provides focus and encourages the team to work together rather than on separate initiatives

A single coherent Sprint Goal fosters focus and collaboration toward one objective.

What is a key sign that Sprint Planning was effective?

Answer: The team leaves with a clear Sprint Goal and a workable plan they understand

Effective planning produces a shared Sprint Goal and an actionable, understood plan.

Can the Sprint Backlog be updated after Sprint Planning ends?

Answer: Yes, the Developers update it throughout the Sprint as they learn more

The Sprint Backlog is a living plan that Developers update throughout the Sprint.