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 |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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 | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
