The Rules of Scrum: Your ScrumMaster uses the Retrospective to help your team improve its processes and teamwork

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.

Try out our Virtual Scrum Coach with the Scrum Team Assessment tool - just $500 for a team to get targeted advice and great how-to information

Please share!
This entry was posted in Scrum, XP and Lean and tagged , , , , by Mishkin Berteig. Bookmark the permalink.

About Mishkin Berteig

Mishkin Berteig is a Baha'i, a father of four, a husband and an experienced Agile consultant and trainer. Mishkin is a Certified Scrum Trainer (CST) with the Scrum Alliance, a certified Master of OpenAgile with the OpenAgile Centre for Learning and a certified SAFe Program Consultant (SPC) with the Scaled Agile Academy. Mishkin has a technical background including a B.Sc. in Computer Science and worked as a Chief Architect reporting to the CIO of Charles Schwab, but gave it up to be more Agile.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>