The document outlines the key points of a retrospective meeting including: 1. The retrospective is facilitated by the Scrum Master and should include the Product Owner, Scrum Master, and team. 2. The team openly discusses what went well, what didn't go well, and action items for improvement in a collaborative manner. 3. The discussion focuses on process, people, and culture improvements and generates prioritized actions and lessons learned to apply to the next sprint.

1. Retrospective - Key Points
• Meeting is facilitated by Scrum Master
• All attendees should be present – Product Owner, Scrum Master and
Team
• Team should give the open and honest opinion
• Retrospective is a collaboration process by which all attendees will
discuss about the improvement in terms of process, people, and
culture.
• Attendees will identify the below answers (with the below sequence) :
 What went well ?
 What didn’t go well ?
 What are the action items to be improved ?
• The discussion should be healthy process and constructive with
innovative ideas, they should NOT be landed-up into serious argument
• Scrum Master will help team in discovery – NOT provide the answers
• Scrum Master will prioritize the actions and lessons learned based on
the team direction

2. Retrospective - Key Benefits
• Inspects and Adapts – leads improvement from the last sprint to
immediate future sprint
• Increase Transparency between all team members
• Supports Team Formation and Bonding (especially at the areas
conflict can be identified and dealt with)
• Improve Team’s sense of ownership and self-management

3. Six Steps in Retrospective
• Setting the context (Have some preparation before the meeting; ready with
some useful data)
• Set the stage (Set up environment for the meeting)
• Energizer (Be ready with open and honest opinion and get the mindset to put
across boldly)
• Check-in (Focus on the meeting in hand)
• Main Course (Provide the answers with the sequence : a. What went well ? b.
What didn’t go well ? c. What are the action items to be improved ?)
• Filtering (Sort out with the precise data; remove redundant information and
prioritize the data sorted – Scrum Master would be able to do that task with
the help of the team)