Sprint Review

5 minutes 5 Questions

The Sprint Review is an informal meeting held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders discuss what was done in the Sprint, taking into account the market, potential capabilities, and timelines. The Product Backlog may also be adjusted to meet new insights. The presentation of the Increment is key to providing transparency and receiving feedback.

Guide: Understanding the Sprint Review in PSM-I Scrum Methodology

The Sprint Review is a critical part of the Scrum framework. It marks the end of the sprint, where the Scrum Team and stakeholders collaborate to inspect the increment and adapt the Product Backlog based on the feedback.

Importance: The Sprint Review is important because it provides an opportunity for the team to adapt the Product Backlog based on the work done and further discussion. This adaptation can lead to maximizing the value if done correctly.

Function: During Sprint Review, the Scrum Team showcases what they completed in the Sprint. Stakeholders provide feedback, which feeds into the Product Backlog for the next Sprint Planning.

Exam Tips: When answering questions on Sprint Review during an exam, ensure that you haven't confused it with the Sprint Retrospective. The Sprint Review is about the Product, while the Sprint Retrospective is about the team and the process. Recalling the purpose, participants, and outcome of Sprint Review can also be helpful. Always think about the Sprint Review in the context of inspection and adaptation, as this is a principle at the heart of Scrum.

Another important thing to remember is that the Sprint Review is a timeboxed event. It shouldn't exceed one hour for a one-week Sprint. Longer Sprints would proportionally increase the length of the Sprint Review. Understanding timeboxing and being able to effectively manage time is crucial for the Scrum Master role.

Also, expect questions that test your understanding of who attends the Sprint Review and what their roles are. You should know that the Scrum Team and stakeholders are essential participants and that the Scrum Master ensures that the event takes place and that the attendees understand its purpose.
Test mode:
Start practice test

PSM I - Sprint Review Example Questions

Test your knowledge of Sprint Review

Question 1

During the Sprint Review, the Development Team demonstrates the increment that does not meet the 'done' criteria. As a Scrum Master, what would be the best course of action?

Correct Answer: Encourage the Development Team to be transparent about the incomplete increment, pinpointing the learning opportunity for improvement during the Sprint Retrospective.

While it is crucial for the increment demonstrated at the Sprint Review to meet the 'done' criteria, it is equally important to foster an environment of transparency and continuous improvement. The correct action is to encourage openness about the work that is not 'done' and use it as a basis for learning and adaptation in the Sprint Retrospective. Extending the sprint duration goes against Scrum principles, as it undermines the concept of a fixed sprint length and can create unsustainable working habits. Adjusting Backlog priorities is a continuous activity and not directly related to addressing work that doesn't meet the 'done' criteria during the Sprint Review. While enhancing the rigor of daily Scrum meetings can be beneficial, it alone does not address the immediate issue of presenting an incomplete increment during the Sprint Review.

Question 2

During a Sprint Review, the team demonstrates a working functionality, but it is not aligned with business objectives. As a Scrum Master, what steps should you take?

Correct Answer: Encourage a retrospective focused on improving alignment with business objectives for future sprints

The correct answer involves facilitating an environment for continuous improvement and reflection on aligning work with business objectives. Directly modifying the Product Backlog without consultation misses the collaborative aspect of Scrum. Halting development doesn't align with the iterative and incremental nature of Scrum, which emphasizes adapting over stopping. Lastly, while an immediate Sprint planning session for redesign might seem proactive, it could lead to inefficiencies and fatigue without ensuring genuine alignment and understanding, lacking the strategic review and adaptation component critical for realignment in the context of Scrum.

Question 3

The Product Owner did not attend the Sprint Review. As the Scrum Master, what is the best course of action?

Correct Answer: Proceed with the Sprint Review, gathering feedback from stakeholders and the team, and ensure to communicate the outcomes to the Product Owner.

The Sprint Review's purpose is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Master should facilitate the event even in the Product Owner's absence, making sure that the feedback loop is not broken. The correct approach is to proceed with the meeting as scheduled, while ensuring the Product Owner is informed of the outcomes. Rescheduling might disrupt the rhythm of the team and stakeholders, omitting important discussions or making decisions without the Product Owner could lead to misalignment with the product vision.

More Sprint Review questions
15 questions (total)
Start 15 question test

Other Scrum Artifacts concepts

Definition of DoneProduct BacklogProduct GoalProduct OwnerScrum BoardSprint BacklogSprint BurndownSprint GoalSprint Retrospective
All Scrum Artifacts questions · PSM I practice test