The document discusses the importance of the retrospective meeting in Scrum. It notes that early versions of Scrum did not include retrospectives and that they are important for teams to inspect and adapt their processes. Retrospectives provide an opportunity for teams to reflect on what went well and what can be improved in the last sprint and develop an action plan to become more effective. They should be time-boxed, focus on constructive feedback rather than blame, and actively engage the whole team, Scrum Master, and Product Owner to drive process improvements.

1. Deepak T Gururaja

2.  The very first version of Scrum did not have a
retrospective meeting
 Can you think of Scrum as a process without
an avenue to “Inspect and Adapt”

3.  A ceremony conducted at the end of a sprint
 Inspect and Adapt
 The last and the most important Agile
Principle
At regular intervals, the team reflects on how
to become more effective, then tunes and
adjusts its behavior accordingly

4.  Time-boxed
 Attendees restricted only to
 Team
 Scrum Master
 Product Owner
 Scrum Master may or may not be the
facilitator
 The facilitator is just that
 The facilitator does not provide answers

5. Regardless of what we discover, we
understand and truly believe that everyone
did the best job they could, given what they
knew at the time, their skills and abilities,
the resources available, and the situation at
hand.

6.  What was out learning from the sprint
 What did we do well
 What should we do well
 What are the problems that we faced
 Retrospectives are also a place to appreciate
fellow team mates

7.  Come prepared with your inputs
 Points should not be directed to an individual
 Its not so much about what went wrong,
rather about how can we correct it
 Always keep the time box in mind
 Arrive at constructive points for
implementation
 Before leaving the retrospective, have a
clear goal on what the future action plan will
be

9.  It’s the best platform to bring out areas of
improvements
 Provide frank and data-driven insights on the
events that took place in the sprint
 Keep the conversation focused
 Most importantly – Participate actively

10.  Why do you think retrospective is important?
 When do you think a retrospective fails?
 What happens when retrospectives fail?
 Do you think retrospective should take as
long as it takes?
 Can you each identify one benefit of a
retrospective?