The document discusses how to conduct effective agile retrospectives for teams. It provides guidance on setting the stage, gathering data, generating insights, deciding on actions, and closing the retrospective. Key aspects covered include establishing norms, choosing appropriate activities, facilitating discussions, and following up on identified actions. The goal is for retrospectives to help teams continuously improve through reflective learning.

1. Making good teams great!
AGILE
RETROSPECTIVES

2. Let’s everybody
stand-up
and, sit if…

3. Norm Kerth
Project Retrospectives: A Handbook for Team Review
Prime Directive
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.

4. A Retrospective is
neither a name and
shame/blame game
nor a forum to fix all.

5. WHY
What is Retrospective
WHO WHEN HOW LONG INPUT OUTPUT

6. Who are our attendees?

7. Role of a Scrum Master
PEOPLE
Personalities (quiet, passive, aggressive)
Introverts vs. extroverts
YOU
Facilitator vs. team member
Let others talk
TIME
Start and finish on time
Time-box activities
Have breaks

8. Structure of a Retrospective
Set the
stage
Gather
data
Generate
insights
Decide
what to do
Close the
retrospective

9. Set the stage
Structure of a Retrospective
Check-in

10. Gather data
Structure of a Retrospective
Timeline
Starfish
Satisfaction Histogram
Team Radar

11. Generate insights
Structure of a Retrospective
Brainstorming
Identify themes
Grouping - Fishbone
- 5 Why’s

12. Decide what to do
Structure of a Retrospective
Dot voting
Tip the top
Break out

13. Closing the
retrospective
Structure of a Retrospective
End in positive way
Temperature Reading
Appreciation
Celebrate

14. Follow up
Share retrospective results
Make comments and actions visible
Add action items to sprint/learning backlog
Check the status regularly
Review on next retrospective

15. Smells
Reporting to management
Offline retrospective (by email)
Only a few participants
Everybody is happy
Blame game
Nobody talks about the elephant
Too short retrospective meeting
Facilitator doesn’t facilitate

16. Resources
• retromat.org
• liberatingstructures.com
• mccarthyshow.com/online/
• funretrospectives.com
• retrospectivewiki.org
• retrospectives-subscribe@yahoogroups.com
• Retrospectives – LinkedIn Group

17. Thank you convey2rohit@yahoo.com • @growAgile • www.growagile.com

18. Return
on Time
Investment
(ROTI)
USELESS
I really lost my time
USEFUL
It wasn’t worth the 100% time spent
GOOD
I gained more than the time I spent
EXCELLENT
It’s worth more than the time I spent on it
AVERAGE
I gained enough to justify the time spent