How To Facilitate Distribution Retrospectives
summary
Distributed retrospectives are harder but unavoidable and work if you follow concrete practices: prepare asynchronously (share a Google Doc/Drawings timeline and send calendar invites and reminder emails), require everyone on video and track participation, and follow up on measurable action points (example: from Monday every commit must have another reviewer). Watch anti-patterns: prime directive ignorance that kills trust and the Wheel of Fortune of repeating symptoms. Use root-cause tools like 5 Whys/fishbone, limit groups to ~10, and test the tech beforehand.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:36What can go Wrong -Antipatterns for Retrospectives
- 12:24symptoms and problems
- 15:33Retrospectives - Stages and activities Set the Stage
- 38:09Your Personal Improvement • Take a minute to think about all this
related talks
42mTeam Meetings That Don't Suck - Avoid Retrospectives Antipatterns
33mCommon Retrospectives Traps & Solutions
56mESSENTIALS - Retrospectives: Shifting Towards Value
01h 43mProject Retrospectives (Why, How, When)
38mRetrospectives Antipatterns Avoid my Mistakes
30mImproving Software Quality with Retrospectives
01h 57mRetrospectives for everyone
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow