Retrospectives Antipatterns Avoid my Mistakes
summary
Retrospectives get specific fixes not pep talks: she names five stages (setting the stage, gather data, generate insights, decide, close) and seven antipatterns with refactors — Wheel of Fortune (fast three-postit retros hide root causes), in the soup (separate what teams can change), and prime directive (assume people did their best). Tools: fishbone, five whys, think‑pair‑share, timers, dialogue sheets, Nitro; keep actions on the team board, run ~1h15–1h30, and treat action points as experiments tracked after the meeting.
AI-written summary · about
chapters (11)
- 0:00Retrospectives intro
- 3:57Patterns vs anti-patterns
- 5:44Five stages of retro
- 9:36Anti-pattern Wheel of Fortune
- 17:17Deciding retro actions
- 23:00Anti-pattern In the soup
- 26:56Prime directive mindset
- 29:05Anti-pattern The loud mouth
- 31:31Anti-pattern Do it yourself
- 35:00Anti-pattern Poor prep
- 37:49Key takeaways
related talks
59mRetrospectives Antipatterns
42mTeam Meetings That Don't Suck - Avoid Retrospectives Antipatterns
38mTeam Meetings That Don't Suck - Avoid Retrospectives Antipatterns
33mCommon Retrospectives Traps & Solutions
49mRetrospective Anti-Patterns
30mImproving Software Quality with Retrospectives
48mStop Complaining& Start Learning! Retrospectives That Drive Change
48mStop Complaining& Start Learning! Retrospectives That Drive Change