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 Command |  Agile Starfish Retrospective |  Agile Start Stop Continue |
|---|---|---|---|
Purposedifferent | 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 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 | As needed | 45-90 min | 30-60 min |
Participantsdifferent | 4-15 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Incident Log, Action Tracker, Stakeholder Updates | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | IncidentOperationsReliability | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
