Understanding the Purpose of a Sprint Review
The Sprint Review is a crucial event in Scrum that serves as an opportunity for the Scrum Team and stakeholders to inspect the product Increment and adapt the Product Backlog based on feedback and changes in the market or user needs. This event fosters collaboration and ensures that the product development remains aligned with business goals and stakeholder expectations.
Exam Question
What is the purpose of a Sprint Review?
(choose the best answer)
A. To build team spirit.
B. To take time to judge the validity of the project.
C. To review the Scrum Team’s activities and processes during the Sprint.
D. To inspect the product Increment with stakeholders and collect feedback on next steps.
Correct Answer
D. To inspect the product Increment with stakeholders and collect feedback on next steps.
Explanation
Correct Answer
D. To inspect the product Increment with stakeholders and collect feedback on next steps:
The Sprint Review is designed to inspect the product Increment and gather feedback from stakeholders. The Scrum Team presents the work they have completed during the Sprint, and stakeholders provide input on the direction of the product. This feedback is crucial for refining the Product Backlog and planning future Sprints to ensure the product continues to deliver value.
Why the Other Options Are Less Appropriate
A. To build team spirit:
While team spirit is important, it is not the primary purpose of the Sprint Review. The Sprint Review is focused on inspecting the product Increment and gathering feedback, not on team-building activities.
B. To take time to judge the validity of the project:
The Sprint Review is not about judging the validity of the entire project but about inspecting the work completed during the Sprint. It focuses on reviewing the Increment and gathering feedback to adapt the Product Backlog. The overall project validity is continuously assessed throughout the project, but that is not the core purpose of the Sprint Review.
C. To review the Scrum Team’s activities and processes during the Sprint:
Reviewing the Scrum Team’s activities and processes is more aligned with the Sprint Retrospective, not the Sprint Review. The Sprint Retrospective is where the Scrum Team discusses what went well, what could be improved, and how they can work more effectively in future Sprints. The Sprint Review, on the other hand, is focused on the product itself and stakeholder feedback.
Relevance to the PSD Exam
Understanding the purpose of the Sprint Review is essential for the PSD exam. It highlights the importance of stakeholder collaboration and continuous feedback, which are crucial for delivering a product that meets business needs and user expectations.
Key Takeaways
- Sprint Review: A collaborative event where the Scrum Team and stakeholders inspect the product Increment and gather feedback.
- Stakeholder Feedback: Integral to refining the Product Backlog and ensuring that the product continues to deliver value.
- Focus on the Product: The Sprint Review is about the product, not the Scrum Team’s processes or activities.
Conclusion
The Sprint Review is a vital event in Scrum that ensures the product being developed is aligned with stakeholder expectations and business goals. By inspecting the product Increment and gathering feedback, the Scrum Team can adapt their plans and continue to deliver valuable Increments.

Get ready for the official PSD exam
127 PSD practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSD exam fee ($200) is paid separately to Scrum.org.
More PSD exam questions
- Which of the following services are appropriate for a Scrum Master in regard to the Daily Scrum?” (PSD)
- What three things happen when refining Product Backlog items?
- You are asked to refactor part of the codebase for Application X. When you are done, all unit tests pass with 50% code coverage. What can you infer from this?
- What is the practice of branching code in a version control system?
- When can Product Backlog refinement occur?
