View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps Incident Timeline Analysis |  Agile Starfish Retrospective |  Agile Start Stop Continue |  DevOps Blameless Postmortem |
|---|---|---|---|---|
Purposedifferent | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 | Medium | Low | Low | Medium |
Timedifferent | 60-180 min | 45-90 min | 30-60 min | 30-90 min |
Participantsdifferent | 3-10 | 4-12 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Postmortem Doc, Action Items, Timeline |
Tagsno overlap | IncidentTimelineSite Reliability Engineering | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | Site Reliability EngineeringIncidentLearningReliability |