Retrospective
A 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. The purpose of the Sprint Retrospective is to plan ways to increase product quality and effectiveness. The Scrum Master encourages the team to improve, within the Scrum process framework, its development processes and practices to make it more effective and enjoyable for the next Sprint.
Guide on Retrospective
Importance: Retrospective meetings are important as they provide an opportunity for the team to reflect upon the sprint, discuss what went well, areas that need improvement, and addressing those issues before the next sprint starts. The process promotes a culture of continuous improvements, enhances team’s efficiency and ultimately increases their likelihood to reach project's goals.
What it is: Retrospective is a meeting that the team holds at the end of each sprint to inspect their work process and create a plan to improve it for the next sprint.
How it works: It is facilitated by the Scrum Master and involves all the members of the Scrum team. The participants share their thoughts and insights about what worked out well in the sprint, what could be improved, and how these improvements can be implemented.
Exam Tips: Answering Questions on Retrospective: Do remember that Retrospectives are never skipped and considered as a key inspect and adapt opportunity for Scrum Teams. Any questions pertaining to the Retrospective should be addressed with the understanding that it primarily focuses on process improvement. Improvements identified are owned by the Team and implemented as soon as possible. It is not a blame game or a session to point out individual mistakes. Answers should reflect on the element of collaboration, ownership and knowledge sharing within the team. Always keep the Scrum Guide in mind!
PSM I - Retrospective Example Questions
Test your knowledge of Retrospective
Question 1
Despite numerous retrospective meetings and action items, your team keeps encountering the same challenges. As a Scrum Master, how would you address this?
Question 2
During the retrospective, a team member consistently dominates the discussions and others are not getting an opportunity to voice their opinions. As a Scrum Master, what is the most appropriate way for you to handle this scenario?
Question 3
Your team has completed a sprint and it's time for the retrospective meeting. Recently, discussions have become heated and members leave feeling deflated. What should you as a Scrum Master do to improve the situation?