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 |
|---|---|---|---|
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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 60-180 min | 45-90 min | 30-60 min |
Participantsdifferent | 3-10 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | IncidentTimelineSite Reliability Engineering | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
