Practice sprint review communication vocabulary: sprint goal achievement, story completion rates, carryover stories, velocity reporting, and sprint review metrics.
0 / 5 completed
1 / 5
A Scrum Master says 'the sprint goal was achieved'. What does this mean even if not all stories were completed?
The sprint goal is the overarching objective of the sprint, not a list of individual stories. A team can achieve the sprint goal while leaving some stories incomplete — for example, if the goal was 'enable user login' and the core auth stories are done, the goal is met even if a minor UI story carries over.
2 / 5
The team says 'we completed 7 of 9 stories'. How should incomplete stories be handled?
Incomplete stories (stories not meeting their definition of done by sprint end) carry over to the next sprint. Their original estimates are retained — the team doesn't re-estimate work already partially done. The PO may choose to re-prioritise them in the next sprint planning.
3 / 5
'The incomplete story carries over.' What should the team communicate about a carryover story?
Good communication about carryover stories includes: how much work remains, what prevented completion (dependency, scope growth, unexpected complexity), and whether the remaining work fits within the original estimate. This helps the team plan the next sprint accurately.
4 / 5
'The team velocity this sprint was 34 points.' How is velocity used in Scrum?
Velocity is the average number of story points a team completes per sprint. It's used to forecast future sprint capacity and release dates. A velocity of 34 points means the team can plan roughly 34 points for the next sprint — though velocity fluctuates and should be averaged over 3-5 sprints.
5 / 5
What are 'sprint review metrics' typically reported to stakeholders?
Sprint review metrics for stakeholders focus on delivery outcomes: how many stories were completed vs planned, the sprint goal status (achieved/not achieved), current velocity trend, and carryover items. These metrics give stakeholders a clear picture of progress without getting into technical implementation details.