In a Scrum context, a Sprint is a set period (usually between one and four weeks) during which specific work has to be completed and made ready for review. The Sprint Review, therefore, is a meeting where the Scrum team shows what they shipped in the Sprint.
The principle behind the Sprint Review is to garner feedback on the product incrementally and make the necessary changes before the next Sprint begins. Under the guidance of a ScrumMaster, the session allows stakeholders to comprehend the product’s current state and facilitate a discussion about what to do in the next Sprint.
Key Participants in a Sprint Review
The Sprint Review involves critical players including the ScrumMaster, the Product Owner, the Development Team, and other stakeholders such as managers, executives, customers, among others. While the ScrumMaster facilitates, the Product Owner presents the increment and the Development Team discusses the work.
Conducting a Sprint Review
Let’s break down the steps involved in performing a Sprint Review:
- Review the Sprint Goal: Review the goals set at the beginning of the Sprint.
- Present the Product Backlog: Product Owner presents the Product Backlog items completed during the Sprint.
- Demonstrate Complete Work: The Developer Team demonstrates the work done and explains challenges faced if any.
- Inspect and Adapt: Hold a conversation about the work done, and discuss the future in terms of what to do next.
- Update Product Backlog: After receiving feedback, update the Product Backlog.
- Review Timeline, Budget, and Capabilities: Discuss if there have been any changes to the projected timelines, budget, or capabilities, and adjust the Product Backlog accordingly.
- Close the Sprint Review: The ScrumMaster closes the meeting, ready to facilitate the proceeding Sprint Retrospective.
Sprint Review Vs. Sprint Retrospective
While both are important in Scrum methodology, they serve different purposes.
| Sprint Review | Sprint Retrospective | |
|---|---|---|
| Focus | Product Increment | Process improvements |
| Key Participants | Scrum Team, Stakeholders | Scrum Team only |
| Key Questions | What was done? What can be improved product-wise? | What went well? What could improve teamwise? |
| Output | Updated Backlog, Revised Plans | Action-items for team improvement |
Understanding this distinction and facilitating both effectively is the key role of a ScrumMaster.
Conducting efficient Sprint Reviews is a cornerstone in the effective application of Scrum principles. It requires active facilitation, open discussions, and quick adaptability. As a Certified ScrumMaster, your ability to orchestrate these elements in harmony can make a profound difference in your team’s agility and product quality.
Practice Test
True or False: The primary goal of a Sprint Review is to inspect the incremental product increment created during the current Sprint.
- True
- False
Answer: True
Explanation: The key goal of the Sprint Review is to inspect the features completed during the current Sprint and adapt the work for the next Sprint based on feedback.
Who are typically present in a Sprint Review meeting?
- A. The Development Team
- B. The Product Owner
- C. The Scrum Master
- D. The Stakeholders
Answer: A, B, C, D
Explanation: All individuals play a key role in the Sprint Review meeting – the Development Team demonstrates the work, the Product Owner represents the business, the Scrum Master facilitates and the stakeholders provide essential feedback.
The Sprint Review should typically be followed immediately by the Sprint Retrospective.
- A. True
- B. False
Answer: B. False
Explanation: Ideally, there should be a gap between the Sprint Review and the Sprint Retrospective to allow the team to rest, reflect, and prepare.
Which of the following is not a recommended part of the Sprint Review?
- A. Discussing what went well during the sprint
- B. Demonstrating the completed features
- C. Gathering feedback from stakeholders
- D. Adapt the backlog based on the feedback
Answer: A. Discussing what went well during the sprint
Explanation: Discussing what went well and identifying areas for improvement is the part of the Sprint Retrospective, not the Sprint Review.
True or False: It is mandatory to finish all items in the Sprint Backlog before a Sprint Review can occur.
- True
- False
Answer: False
Explanation: The Sprint Review is intended to show the progress of work, so it need not be fully completed. Unfinished items would be discussed and replanned.
Who is primarily responsible for facilitating the Sprint Review?
- A. Product Owner
- B. Scrum Master
- C. Development Team
- D. Stakeholders
Answer: B. Scrum Master
Explanation: The Scrum Master is the facilitator for the Scrum Team and is responsible for ensuring that the team adheres to Scrum theory, practices, and rules.
True or False: The Sprint Review is a formal meeting that follows a strict agenda.
- True
- False
Answer: False
Explanation: The Sprint Review is a more relaxed, open session where feedback is encouraged and there is room to adapt the agenda as needed.
What is a key outcome of the Sprint Review?
- A. A list of potential improvements
- B. A revised Product Backlog
- C. Team camaraderie
- D. Certification of completion
Answer: B. A revised Product Backlog
Explanation: One of the central outcomes of the Sprint Review is a revised Product Backlog, which reflects the work to be carried in the next Sprint based on the feedback received.
When does the Sprint Review happen?
- A. Mid-way through the Sprint
- B. Just before the Sprint begins
- C. At the end of every Sprint
- D. Anytime during the Sprint
Answer: C. At the end of every Sprint
Explanation: The Sprint Review is conducted at the end of each Sprint to inspect the work done and adapt the backlog based on this review.
True or False: Customers are not allowed to participate in a Sprint Review.
- True
- False
Answer: False
Explanation: The presence of customers or end-users during a Sprint Review can be beneficial for directly receiving feedback and ensuring that the product increment is valuable to them.
Interview Questions
What is the main purpose of a Sprint Review in Scrum?
The Sprint Review is an opportunity for the Scrum Team to inspect the increment of product development and adapt the product backlog based on feedback.
Who are the attendees of a Sprint Review?
The attendees of a Sprint Review include the Scrum Team (Product Owner, Scrum Master, Development Team), stakeholders, customers, and anyone interested in understanding the progress made during the Sprint.
What elements are typically included in a Sprint Review?
A Sprint Review typically includes a demo of the work done during the Sprint, a discussion about what went well and what could be improved, an update of the Product Backlog, and a review of the timeline, budget, and potential capabilities for the next anticipated release of the product.
How long is a Sprint Review supposed to last?
For a four-week Sprint, a Sprint Review should not exceed four hours. For shorter Sprints, it is usually scaled down proportionately.
Who leads a Sprint Review?
The Product Owner leads the Sprint Review with the support of the Scrum Master.
Can the Sprint Review be used to suit up new features that aren’t done?
No, only features that meet the team’s definition of “Done” should be presented at the Sprint Review.
What is the difference between a Sprint Review and a Sprint Retrospective?
While both are events that conclude a Sprint, the Sprint Review focuses on the product increment created during the Sprint and feedback for product backlog refinement, while the Sprint Retrospective focuses on the team’s improvement for the next cycle.
Is it necessary to demonstrate every single item completed during the Sprint in the Review?
While it is strongly recommended to demonstrate the increment of the product, it isn’t mandatory to go through every single item. The team should focus on showcasing the most important features completed during the Sprint.
What happens to the Product Backlog after a Sprint Review?
After a Sprint Review, the Product Backlog may be revised to include new insights generated from the discussion. This could mean adding, deleting, or prioritizing items.
What happens if a stakeholder can’t attend a Sprint Review?
It should still proceed as scheduled. The Scrum Master and Product Owner can keep absent stakeholders informed about the outcomes of the Sprint Review afterwards.
How do we inspect the product during the Sprint Review?
During the Sprint Review, inspecting the product most often involves demonstrating the new functionality of the product increment.
What kind of feedback might you expect during a Sprint Review?
Feedback during a Sprint Review might include responses to the product increment, suggestions for subsequent Sprints, technical challenges, shifts in the marketplace, or potential adjustments to the timeline or priorities.
Can a Sprint Review be skipped?
In Scrum, no event is optional and skipping a Sprint Review means that the team misses the opportunity to inspect and adapt the product increment.
Does every feedback received in Sprint Review need to result in Product Backlog changes?
While all feedback should be considered, it’s up to the Product Owner to determine the best way to adjust the Product Backlog based on the feedback given.
What should be done if a story is not “Done” by the Sprint Review?
If a story is not “Done”, it should not be demonstrated in the Sprint Review and it typically goes back to the Product Backlog for consideration in future Sprints.
extutorials.com