Sprint Planning & Estimation Flashcards
7 cards from real CAE practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Sprint Planning & Estimation flashcards as text
During sprint planning, the team realizes the top-priority backlog item is too large to complete in one sprint. What is the BEST course of action?
Answer: Break the item into smaller stories that fit within the sprint
Large user stories should be split into smaller, sprint-sized pieces that can be completed within the timebox.
What does 'relative estimation' mean in the context of agile story pointing?
Answer: Sizing stories by comparing their complexity to each other rather than to absolute time
Relative estimation compares the size and complexity of stories against one another rather than converting directly to hours or days.
A Scrum team's velocity has varied between 30 and 50 points over the last six sprints. How should the team use this data for sprint planning?
Answer: Use the average velocity as a forecasting guideline
Average historical velocity provides a reliable baseline for forecasting how much work the team can realistically complete.
What is the primary purpose of the sprint goal established during sprint planning?
Answer: To provide a single coherent objective that gives the sprint focus and meaning
The sprint goal is a short, focused objective that aligns the team's work and allows flexibility in how it is achieved.
Which technique involves assigning story points using a sequence like 1, 2, 3, 5, 8, 13 to reflect increasing uncertainty at larger sizes?
Answer: Fibonacci sequence estimation
Fibonacci-based estimation captures the inherent uncertainty in larger items by widening gaps between higher values.
When should the development team decompose selected backlog items into tasks during sprint planning?
Answer: During the second part of sprint planning, after the sprint goal is set
In the second part of sprint planning the team breaks down selected stories into actionable tasks to create their sprint plan.
A new team member joins mid-project and the team's velocity drops for two sprints. How should the Scrum Master handle sprint planning capacity?
Answer: Temporarily adjust planned capacity downward to account for onboarding overhead
Acknowledging onboarding overhead by reducing planned capacity prevents overcommitment during the ramp-up period.