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 |  Agile Start Stop Continue |  Agile NoEstimates |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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. | 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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 45-90 min | 30-60 min | laufend | 30-90 min Setup, danach laufend |
Participantsdifferent | 4-12 | 3-12 | 2-12 | 1-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Throughput Data, Flow Forecast, Slicing Rules | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | EstimationForecastingFlow | ForecastingFlowDelivery |