View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sprint Retrospective |  DevOps Blameless Postmortem |  Facilitation Fishbowl Discussion |
|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | When a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-90 min | 45-90 min |
Participantsdifferent | Scrum Team | 3-12 | 8-80 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Improvement actions, Team agreements | Postmortem Doc, Action Items, Timeline | Discussion Insights, Observed Tensions, Follow-up Questions |
Tagsno overlap | RetrospectiveImprovementLearning | Site Reliability EngineeringIncidentLearningReliability | FacilitationDialogueLarge group |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
