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 Starfish Retrospective |  DevOps Incident Command |  Agile 4Ls Retrospective |  DevOps Blameless Postmortem |
|---|---|---|---|---|
Purposedifferent | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | As needed | 45–75 min | 30-90 min |
Participantsdifferent | 4-12 | 4-15 | Team members involved | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Incident Log, Action Tracker, Stakeholder Updates | 4Ls Board, Learning Themes, Improvement Actions | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | IncidentOperationsReliability | RetrospectiveLearningReflectionTeam | Site Reliability EngineeringIncidentLearningReliability |