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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.
Complexitydifferent
LowHigh
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-4 Wochen
Participantsdifferent
Scrum Team1-6
Formatdifferent
WorkshopAsync
Outputdifferent
Improvement actions, Team agreementsExperiment results, Decision log, Learning summary
Tagsno overlap
RetrospectiveImprovementLearning
ExperimentsGrowthAnalyticsValidation
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Growth Experiment workspace showing the question, observations, and next decision.
Growth
Growth Experiment
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective