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 Sprint Retrospective |  Growth A/B Testing |  Product Discovery Smoke Test |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 1-4 Wochen | 1-5 Tage | 45-90 min |
Participantsdifferent | Scrum Team | 1-6 | Nutzertraffic | 4-12 |
Formatdifferent | Workshop | Async | Async | Workshop |
Outputdifferent | Improvement actions, Team agreements | Experiment results, Decision log, Learning summary | Interest Metrics, Conversion Signal, Learning Note | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementLearning | ExperimentsGrowthAnalyticsValidation | ValidationExperimentsDemandGrowth | RetrospectiveImprovementExperimentsTeam |