Team Meetings That Don't Suck - Avoid Retrospectives Antipatterns
summary
Six concrete anti‑patterns and fixes: retrospectives often trade symptoms for root causes so teams should follow the five phases (set the stage, gather data, generate insights, decide, close), use start/stop/continue sparingly, dig with 5 Whys or an Ishikawa diagram, and assign a named owner for experiments. Use anonymous input (Google Drawings or online retro tools), a team radar, circle-of‑influence sorting, think‑pair‑share or Liberating Structures, rotate facilitators, insist on video, prepare the agenda and prework, and never record.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:30Retrospectives
- 2:34Retrospective Time
- 3:07Antipatterns
- 5:19Patterns
- 6:11Retrospective
- 7:20Wheel of Fortune
- 8:08Stop Continue Posters
- 11:55The Refactored Solution
- 14:14Fishbone Diagram
- 15:37Deciding what to do
- 16:52The life of any meeting
- 22:13In the soup
- 28:22Refactoring
- 29:23Loudmouths
- 32:06Do it yourself
- 34:31insist on video
- 37:58Questions
related talks
38mRetrospectives Antipatterns Avoid my Mistakes
33mCommon Retrospectives Traps & Solutions
44mHow To Facilitate Distribution Retrospectives
56mESSENTIALS - Retrospectives: Shifting Towards Value
15mThe seven deadly sins of retrospectives
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow
30mImproving Software Quality with Retrospectives
01h 43mProject Retrospectives (Why, How, When)