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 Start Stop Continue |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | 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. | 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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. |
Complexitydifferent | Low | High | Low |
Timedifferent | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 3-12 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
