Practice sprint review communication vocabulary: sprint goal achievement, story completion rates, carryover stories, velocity reporting, and sprint review metrics.
0 / 10 completed
1 / 10
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 / 10
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 / 10
'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 / 10
'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 / 10
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.
6 / 10
Alex, the junior developer, just submitted a pull request with a significant refactoring of the user authentication module. During the code review, you noticed several comments from Sarah regarding potential security vulnerabilities. What's the most effective way to respond directly to her in Slack?
This scenario tests proactive communication during code review. Simply dismissing concerns isn't helpful. The best approach is to acknowledge Sarah's feedback and propose a collaborative discussion to ensure everyone understands the rationale and mitigations. Ignoring the comments risks missing critical security issues.
7 / 10
Ben, the product owner, is presenting the sprint review. He states, 'The team delivered a fully functional version of the user profile update feature.' However, several stakeholders are asking about the integration with the payment gateway, which was initially planned for this sprint but wasn't completed. How should Ben frame this to manage expectations?
This assesses communication about incomplete stories during a review. Ben needs to acknowledge what *was* delivered while transparently explaining why other items were deferred. Framing the conversation around dependencies and future planning builds trust and manages stakeholder expectations, rather than simply dismissing their questions.
8 / 10
Chloe writes in the pull request description: 'Fixed a bug reported by QA.' What additional information should she include to provide clarity and context for reviewers and future developers?
A good pull request description goes beyond simply stating what was fixed. Providing details about the nature of the bug—in this case, a 'race condition'—significantly improves understanding and facilitates future maintenance or debugging efforts. Vague descriptions hinder collaboration.
9 / 10
During the daily standup, David says, 'I spent yesterday working on the database schema migration.' What follow-up question should the Scrum Master ask to gain more insight and ensure David's work aligns with the sprint goal?
The Scrum Master's role is to facilitate productive standups. This question probes not just *what* David did but also *how* he approached the task and its relevance to the sprint goals. Understanding challenges helps identify potential roadblocks and ensures alignment.
10 / 10
The team's sprint review is concluded. The stakeholders are asked for feedback on the delivered functionality. They request a report detailing 'sprint review metrics.' Which of the following would be most relevant to include?
Sprint review metrics provide valuable insights into team performance. While numerous data points exist, a burn-down chart combined with velocity and story count gives a holistic view of sprint progress and helps identify trends for future sprints. Focusing solely on time spent is an unproductive metric.
What will I learn from the "Sprint Review Communication" exercise?
Practice sprint review communication vocabulary: sprint goal achievement, story completion rates, carryover stories, velocity reporting, and sprint review metrics.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Sprint Demo & Releases exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss sprint demo & releases topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Sprint Demo & Releases exercises?
See the full Sprint Demo & Releases exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.