Sprint Retrospective

5 minutes 5 Questions

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. It is held after the Sprint Review and before the next Sprint Planning. The Sprint Retrospective is crucial to the principle of inspection and adaptation that are central to Scrum framework. Reflection on the process allows for the identification of strengths and weaknesses, and fosters continuous improvement.

Sprint Retrospective - Guide and Exam Tips

The Sprint Retrospective is a crucial part of the Scrum framework, giving teams the opportunity to reflect on their work and identify improvements for future sprints.

What it is: The Sprint Retrospective is a meeting that occurs after the Sprint Review and before the next Sprint Planning. It allows the Scrum Team to reflect on the past sprint and discuss what worked well and what didn't. Output from this meeting includes the identification of improvements that could make future sprints more successful.

Why it is important: Sprint Retrospective is vital as it promotes a continuous improvement culture within the team. It provides an opportunity for the team to inspect themselves and create a plan for adaptations to be enacted during the subsequent sprint.

How it works: The meeting usually lasts for 1.5 hours for a two-week Sprint. The team identifies what went well, what didn't go so well and what could be improved. This data is then used to formulate an actionable improvement plan for the next sprint.

Exam Tips: Answering Questions on Sprint Retrospective:
1. When answering questions related to Sprint Retrospective, keep in mind the purpose of this meeting - reflection and improvement.
2. Ensure you understand the difference between Sprint Retrospective and other Scrum ceremonies.
3. Remember that the team should leave with an actionable plan to improve their workflow in the next sprint.
4. Questions may require you to identify the timing of Sprint Retrospective within Scrum framework or its duration.
5. You could be asked to distinguish between what should and should not be discussed during a Sprint Retrospective.
Test mode:
Start practice test

PSM I - Sprint Retrospective Example Questions

Test your knowledge of Sprint Retrospective

Question 1

The team finds out during the Sprint Retrospective that one team member consistently takes on more tasks. As Scrum Master, how should you handle this situation?

Correct Answer: Encourage the team to review their Definition of Done to ensure it encourages balanced contributions from all members.

The correct answer promotes the idea of the team self-organizing to address workload balance by reflecting on their Definition of Done, ensuring it fosters balanced contributions. Assigning tasks at the beginning of the Sprint or limiting tasks goes against the principles of self-organization and flexibility in Scrum. Adjusting backlog priority based on team member capabilities can create an environment that discourages growth and adaptation, as it doesn't encourage team members to stretch their skills or collaborate to tackle challenging tasks.

Question 2

During the Sprint Retrospective, the team realizes they are not utilizing tools efficiently, leading to decreased productivity. What should the Scrum Master do?

Correct Answer: Encourage the team to explore and evaluate their current tools, suggesting they identify inefficiencies and improvements.

As a Scrum Master, the goal is to foster self-organization and continuous improvement within the team. The correct answer involves encouraging the team to reflect on and optimize their use of tools, without prescribing a specific course of action. The wrong answers either suggest taking actions that are too drastic, not based on self-organization principles (such as immediately switching tools or eliminating them entirely), or promote stagnation (maintaining the status quo), which contradicts the agile principle of embracing change to improve productivity and deliver value.

Question 3

A team member consistently avoids sharing stand-up updates during the Sprint Retrospective. How should the Scrum Master handle this situation?

Correct Answer: Engage in a private discussion with the team member to understand their concerns and encourage open communication.

The best approach for a Scrum Master when a team member consistently avoids sharing updates during the Sprint Retrospective is to engage in a private discussion to understand their concerns and encourage open communication. This approach is direct and respectful, addressing the issue without public confrontation or making the team member uncomfortable. The wrong answers, although potentially beneficial in certain contexts, do not address the root problem as effectively as a private, understanding discussion. Adjusting the retrospective format or discussing the issue with the entire team might help, but could also avoid directly solving the problem, and assigning a mentor might not address the specific issue of reluctance to share in a retrospective.

More Sprint Retrospective questions
24 questions (total)
Start 24 question test

Other Scrum Artifacts concepts

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