# Sprint Planning — Quiz

## Question 1

In Scrum, what are the two parts of sprint planning?

A) Estimate and commit
B) What and how
C) Scope and schedule
D) Backlog and capacity

<!-- ANSWER: B -->
<!-- EXPLANATION: The Scrum Guide defines sprint planning as having two parts: (1) What can we achieve?—the Product Owner presents the goal and proposed items; (2) How will we build it?—the Development Team plans tasks and approach. -->

## Question 2

What is the main purpose of a sprint goal?

A) To list all stories in the sprint
B) To create a single, cohesive objective that guides trade-offs
C) To satisfy stakeholders
D) To track velocity

<!-- ANSWER: B -->
<!-- EXPLANATION: The sprint goal is a unifying objective. When the team faces trade-offs mid-sprint, they ask: "Does this support the goal?" Instead of a list of features, it describes the outcome they're aiming for. -->

## Question 3

Velocity and capacity differ in that:

A) Velocity is in hours, capacity is in points
B) Velocity is historical throughput; capacity is planned available time
C) Velocity is set by the Product Owner; capacity by the Scrum Master
D) They are the same thing

<!-- ANSWER: B -->
<!-- EXPLANATION: Velocity = how many points the team typically completes (measured after the sprint). Capacity = how much person-time is available (planned before the sprint). Capacity helps you sanity-check; velocity helps you forecast. -->

## Question 4

Which estimation technique encourages discussion and surfaces assumptions?

A) T-shirt sizing
B) Hours
C) Planning poker
D) Random guessing

<!-- ANSWER: C -->
<!-- EXPLANATION: Planning poker involves private voting, reveal, and discussion of outliers. The conversation—"Why did you pick 8?"—surfaces hidden assumptions, dependencies, and knowledge gaps. The estimate is secondary to the alignment. -->

## Question 5

A common anti-pattern in sprint planning is:

A) Writing a clear sprint goal
B) Estimating in story points
C) Over-committing to 100%+ of velocity
D) Using a Definition of Ready

<!-- ANSWER: C -->
<!-- EXPLANATION: Over-commitment leaves no buffer for unknowns, interrupts, or discovery. Teams often load the sprint to 100% or more of past velocity, then spill work or cut quality. A healthier approach is 80–90% to leave slack. -->

## Question 6

In Scrum, the team commits to:

A) Delivering every story in the sprint backlog
B) The sprint goal
C) A fixed scope with no changes
D) Completing all tasks in the first week

<!-- ANSWER: B -->
<!-- EXPLANATION: The team commits to the sprint goal—the outcome they're aiming for. The product backlog items selected are a forecast, not a contract. Scope can be rebalanced as the team learns, as long as the goal remains valid. -->

## Question 7

<!-- VISUAL: quiz-drag-order -->

Put these Scrum sprint ceremonies in the order they occur within a sprint:

A) Sprint Review
B) Sprint Retrospective
C) Sprint Planning
D) Daily Scrum (each day)

<!-- ANSWER: C,D,A,B -->
<!-- EXPLANATION: Sprint starts with planning. Daily Scrum runs each day. At the end, Sprint Review (inspect the increment) and Sprint Retrospective (improve the process) close the sprint. -->

## Question 8

<!-- VISUAL: quiz-drag-order -->

Put these story refinement steps in the correct order:

A) Split or combine as needed
B) Ensure Definition of Ready is met
C) Clarify acceptance criteria
D) Estimate (planning poker or similar)
E) Discuss and ask questions

<!-- ANSWER: E,C,A,D,B -->
<!-- EXPLANATION: Refinement starts with discussion and questions to clarify. Define acceptance criteria, then split or combine stories. Estimate, and finally verify the Definition of Ready before adding to the sprint. -->