Retrospectives

A Sprint retrospective is a collaborative meeting that should happen at the end of every sprint, where the team reflects on what went well, what did not, in order to adapt and improve.

Tips:

• Try to retrospect on how you work, not what you did. Look for opportunities to improve the way you collaborate, communicate, quality, testing practices, release frequency, etc.
• The web is a great resource to identify techniques and formats to keep your retrospective fresh. The following is a list of external resource that might help get you started:
  • Retrospective techniques
• According to Scrum Guidelines, the retrospective is a ceremony for the dev team. Scrum does not prescribe to include the Product Owner, project sponsors or other business stakeholders. A rule of thumb might be to expand the retrospective ceremony only as long as the team can still inspect their delivery with candidness and safety. A retrospective will not identify opportunities unless the team is comfortable sharinginformation.