View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Accountability Ladder |  DevOps Blameless Postmortem |  Agile Sprint Retrospective |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-45 min | 30-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-90 min |
Participantsdifferent | 1-8 | 3-12 | Scrum Team | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Ownership Reflection, Action Commitment, Coaching Notes | Postmortem Doc, Action Items, Timeline | Improvement actions, Team agreements | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ResponsibilityLeadershipTeam | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveImprovementLearning | RetrospectiveImprovementExperimentsTeam |