Back to Scrum Tools and Techniques

Sprint Review

5 minutes 5 Questions

The Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. The Scrum Team presents the completed work to the stakeholders and the Product Owner determines which items are done and accepted. This is a great time for the team to demonstrate what they have done, get feedback and make any necessary changes to the Product Backlog. The review meeting gives everyone a good understanding of what was accomplished in the Sprint and aligns the team on next steps.

Guide to Sprint Review

The Sprint Review is a vital part of the Scrum methodology. It provides a platform for the Scrum Team and the stakeholders to inspect the outcome of the work and adapt the Product Backlog if necessary.

What is Sprint Review?
Sprint Review, sometimes referred to as a Sprint Demo, is an event which occurs at the end of every Sprint in the Scrum framework. It is an opportunity for the team to showcase what they have accomplished in the sprint, get feedback, and adjust the future plans if needed.

Why is it important?
Sprint Review is important because it allows everyone involved in the project to stay informed about the progress, and gives a chance to inspect and adapt the product increment. This review also promotes transparency and collaboration, and verifies that this increment is Done.

How does it work?
During the Sprint Review, the Scrum Team and stakeholders collaborate on what was done during the Sprint. Based on that and changes to the Product Backlog during the Sprint, discussions will determine what the next steps could be.

Exam Tips: Answering Questions on Sprint Review
• Try to understand the purpose and function of the Sprint Review rather than merely remembering its definition.
• Questions often relate to stakeholder involvement in the Sprint Review. Remember that it is a time for Inspect and Adapt.
• Understand that the Sprint Review is a platform for open discussion and collaboration, not a blame game.
• Remember, a Sprint Review is not a sign-off meeting.

Test mode:
Start practice test
CSM - Scrum Tools and Techniques Example Questions

Test your knowledge of Amazon Simple Storage Service (S3)

Question 1

In a sprint review meeting, the team demonstrated a feature that was not fully developed. It is being disagreed upon whether to include it in the increment or not. How should the ScrumMaster address this?

Correct Answer: Advocate for adhering to the Definition of Done and only include features that meet these criteria in the increment.

In Scrum, the increment must be in a usable condition and meet the Scrum Team's definition of 'Done' at the end of the Sprint, regardless of whether the Product Owner decides to release it. The ScrumMaster should guide the team to understand and follow this principle, ensuring that only fully developed features are included in the increment. This maintains quality and transparency. Other options might seem reasonable but could lead to technical debt, lower quality, or misunderstandings about the state of the product.

Question 2

During a Sprint Review, the Product Owner introduced new stakeholders who were displeased with the progress. How should the ScrumMaster handle the situation?

Correct Answer: By illustrating the iterative nature of Scrum, showing how progress and feedback are cyclical with each Sprint. Offering to bring new stakeholders up to speed in a separate session.

The correct approach emphasizes the adaptive and iterative principles of Scrum, allowing for continuous feedback, learning, and adaptation. Incorporating new stakeholder feedback is vital, but it must be done within the structure of the Scrum framework, without compromising the current Sprint's goals or the Development Team's workflow. Option one is incorrect because it encourages unsustainable work habits that go against Scrum values. Option two disrupts the current Sprint and undermines the importance of adhering to Sprint goals. Option three is incorrect as it involves handling the situation in a non-collaborative and non-transparent manner, which could impact the open culture that Scrum encourages.

Question 3

During the Sprint Review, a major bug was discovered in the increment. How should this be handled?

Correct Answer: The ScrumMaster should ensure that the Product Owner adds this bug to the Product Backlog to be addressed in future sprints.

In Scrum, when a bug is discovered during the Sprint Review, the best course of action is to document it in the Product Backlog to be addressed in future sprints. This is because the Scrum Team aims to deliver potentially shippable increments of product at the end of each Sprint. If an issue is found, it's logged for further study, prioritized and then rectified in the upcoming sprints based on its priority. This is what the first answer suggests. The other answers are incorrect because in Scrum, ignoring the bug is not acceptable - transparency is key in Agile practices. Insisting the team fix the bug immediately during the Sprint Review is also not right because this time is reserved for feedback and review, not for active problem-solving. Finally, blaming the team for presenting a faulty increment does not align with the values of Scrum, which emphasize shared responsibility, openness and collaboration.

Go Premium

Certified ScrumMaster Preparation Package (2024)

  • 3861 Superior-grade Certified ScrumMaster practice questions.
  • Accelerated Mastery: Deep dive into critical topics to fast-track your mastery.
  • Unlock Effortless CSM preparation: 5 full exams.
  • 100% Satisfaction Guaranteed: Full refund with no questions if unsatisfied.
  • Bonus: If you upgrade now you get upgraded access to all courses
  • Risk-Free Decision: Start with a 7-day free trial - get premium features at no cost!
More Sprint Review questions
28 questions (total)
Start 28 question test