How to conduct effective retrospective session? Here are some common mistakes and suggestions how you can avoid them.

1. Making Good Teams Great
Through Agile Retrospectives!
By Margarita Gevorgyan
From SFL

2. Objectives
1. Change the way we think about
Retrospectives
2. Discuss main issues/mistakes
3. How to make the session more engaging
for development team.
a

3. Purpose of Retrospective Session
a

4. Retrospective in Scrum

5. Main issues with this meeting
• Easy to get bored
• Are considered as waste of time by
developers
• And as a result can be skipped easily

6. Possible result of skipping it:
a

7. Hidden reasons
1. Simply they are not conducted
effective enough
2. Absence of proper follow up-ing
mechanism

8. Helping Your Team Inspect and
Adapt
1. Set the stage
2. Gather data
3. Generate insights
4. Decide what to do
5. Close the retrospective.

9. Change the format as much as
possible!
images
http://retrospectivewiki.org/index.php?title=Retrospective_Plans

10. Leading Retrospectives
1. Focus on the process and structure
2. Help the group reach their goal
3. Retrospective leaders remain Neutral
4. Watch out for people who are talking
more

11. Follow up-ing the decisions made
during the meeting
Visualize
Have assignees
Remind before starting the sprint

12. Appreciations
Image here

13. Summary
1. Change the format often
2. Follow up action points
3. End with something very positive!
(Appreciations, Happiness metric…)
4. Keep in mind to use it as technic for
Empowerment and Enjoyment for your
teams.

14. And remember! Never ever
skip it 
a

15. Thank you !
a