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 | ![]() Agile Starfish Retrospective | ![]() Agile NoEstimates |
|---|---|---|---|
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. | 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 estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | laufend |
Participantsdifferent | 3-12 | 4-12 | 2-12 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | EstimationForecastingFlow |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






