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 |  Operations Failure Mode and Effects Analysis |  Agile Start Stop Continue |
|---|---|---|---|
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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | Low | High | Low |
Timedifferent | 45-90 min | 2-6 h | 30-60 min |
Participantsdifferent | 4-12 | 3-10 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | FMEA Table, Risk Priority, Mitigation Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | RiskQualityOperationsRoot cause | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
