Sprint Planning and Goals Flashcards

What characteristic should a good Sprint Goal have?

Answer: It provides a single coherent objective and flexibility on scope

A Sprint Goal gives the team a coherent objective while allowing flexibility in the exact work to achieve it.

Can the scope of a Sprint be clarified and renegotiated during the Sprint?

Answer: Yes, between the Product Owner and Developers as more is learned

Scope may be clarified and renegotiated with the Product Owner as more is learned, without endangering the Sprint Goal.

Once committed, when can the Sprint Goal itself be changed?

Answer: It remains fixed; only its scope is renegotiated, and it changes via cancellation if obsolete

The Sprint Goal stays the commitment for the Sprint; if it becomes obsolete the Product Owner may cancel the Sprint.

How detailed must the Sprint Backlog be by the end of Sprint Planning?

Answer: Enough that the Developers can inspect progress at the Daily Scrum

The plan should be detailed enough for the Developers to inspect their progress during the Daily Scrum.

Who may attend Sprint Planning besides the Scrum Team?

Answer: Other people invited by the Scrum Team to provide advice

The Scrum Team may invite others to attend Sprint Planning to provide advice.

What should the Developers do with selected items during the 'how' discussion?

Answer: Decompose items into smaller work items as needed

Developers decompose selected Product Backlog items into smaller work items to create a plan.

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

Answer: The Sprint Goal is a step toward the Product Goal

Each Sprint moves the product closer to the larger Product Goal.