methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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 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.
Complexitydifferent
MediumLowLowHigh
Timedifferent
30-60 min5-20 min1-5 Tage1-4 Wochen
Participantsdifferent
2-63-20Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleEffort Heatmap, Risk Signals, Discussion TargetsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
BacklogIterationDelivery
EstimationEffortRisk
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods