The retrospective is the most important event in your agile transformation journey (with Scrum or other framework). Here's an intro on what a successful retrospective is and links to sources.
3. One Rule “Regardless of what we discover, we must understand and
truly believe that everyone did the best job he or she could,
given what was known at that time, his or her skills and
abilities, the resources available, and the situation at hand.”
- Norman L. Kerth -“Project Retrospectives: A Handbook
for Team Reviews”
4. How do you know a
retrospective was successful?
Action items consistently implemented ->
team growth
5. How to lead a successful retrospective?
• Trust
• Safe space
• “What we discuss in the retro
stays in the retro”
• All team present
• Face-2-face
• Time for self-reflection
• Problem solving
• Systems thinking
• Prioritise
• No electronics / distractions
6. Retrospective structure
1. Set the stage
1. Welcome, appreciation, expectations
2. Outline approach
3. Discuss time box
2. Gather data
3. Generate insights
4. Decide what to do
5. Close the retrospective
7. Popular types of retrospectives
What went well / What can be improved / Free
KISS (Keep / Improve / Stop / Start)
LLL (Liked / Learned / Lacked)
Release retrospectives
8. Further learning
Tasty Cupcakes: hundreds of retrospective models
Fun retrospectives
Retrospective wiki
Norman L. Kerth -“Project Retrospectives: A Handbook
for Team Reviews”
Esther Derby, Diana Larson - “Agile Retrospectives:
Making Good Teams Great”
Roger M. Schwartz - “The Skilled Facilitator: A
Comprehensive Resource for Consultants, Facilitators,
Coaches, and Trainers”