This document discusses retrospectives, which are meetings where teams reflect on how to improve effectiveness. It explains that retrospectives are important for continuous improvement. Reasons to change retrospectives include getting stuck in routines, repeatedly facing the same issues, and lack of progress on problems. Different frameworks are presented for retrospectives, including Sailboat for identifying help/hindrances, Starfish for reviewing practices, and Three Little Pigs for evaluating processes and teamwork. Tips are provided such as using dot voting and rotating the facilitator role. Distributed tools for remote retrospectives are also listed.

1. RETROSPECTIVES

2. AGENDA
• What is a Retrospective?
• Why are Retrospectives Important?
• Why change your Retrospective?
• Different Frameworks
• Exercise

3. WHAT IS A RETROSPECTIVE?
“If you adopt only one Agile practice, let it be retrospectives.
Everything else will follow.” Woody Zuill

4. WHY ARE RETROSPECTIVES IMPORTANT?
At regular intervals, the team reflects on how to become more effective,
then tunes and adjusts its behavior accordingly. Agile Principles (#12)

5. WHY CHANGE YOUR RETROSPECTIVES?
REASONS TO CHANGE
• In a rut
• Repeated issues surfacing
• No action items
• Unable to solve problems
• Lack of ownership
TRY CHANGING THE
• Goal
• Environment
• Facilitator
• Framework

6. FRAMEWORK: Sailboat
•Great for identifying the things that help
the team move faster and the things that
slow the team down
–Try adding an obstacle
–Try Hot Air Balloon
•Best time to try: when a team is not
voicing blockers or impediments during
the sprint
•Why? Because it will identify the cause of
issues that the team is facing

7. FRAMEWORK: Starfish
•Great for extracting information while
reviewing practices and the value the team
gets from practices
•Best time to try: when a team goes
through several ups and downs
•Why? Because It will reveal both positive
and less positive things achieved by a
team.
–Try the 4L’s

8. FRAMEWORK: Three Little Pigs
•Great for helping the team evaluate
processes and how they (the team
members) work with each other.
–Try Worked Well, Kinda Worked, Didn’t
Work
•Best time to try: when a team is looking
for areas of improvement
•Why? Because it will foster a conversation
about improvements

9. EXERCISE
• Create 3 groups
• Each group will have a Retrospective
• TOPIC: Attending a conference, talk, or Coaching Series
• One person in group volunteer as facilitator

10. SOME TIPS
TRY TO USE…
• Dot voting to pick one issue to solve
• An energizer to start off
• One word check in or check out
• Rotate facilitation role on the team
• A space without a table
• Round Robin to ensure everyone has an
opportunity to share insight
DISTRIBUTED TEAM?
• Ideaboardz
• Fun Retro
• goReflect
• Trello
• ScatterSpoke
• What other tools have you used?

11. WANT MORE INFORMATION?