The Sprint Retrospective is a key meeting where the team discusses how to improve. Like the other meetings in Scrum, the ScrumMaster is responsible for ensuring it occurs and that it is well-facilitated. There are three main purposes of the Sprint Retrospective: honestly review how the last Sprint was conducted in all aspects including skills, relationships, processes, environment, culture and tools; discover the key aspects of the previous Sprint that need to be carried forward or improved; and, plan how the Scrum Team will improve the way it does work. This meeting aids the team in inspecting and adapting the entire use of Scrum and how the team is progressing as a team. The Sprint Retrospective is a check point that helps the team to know its current state, compare to its desired state, identify gaps, and take the needed steps to improve. This meeting is also where the ScrumMaster challenges the team to look deeply at itself and its process without fear. When a Scrum Team fails to hold and participate in this essential meeting, the team is likely to become a Scrum Team in name only without the spirit of Scrum – and therefore lose many of the far reaching benefits that many other Scrum Teams have experienced.
To learn more about using retrospective to help your team improve its processes and teamwork, visit the Scrum Team Assessment.