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
Paper illustration of MVP Test Matrix with a method-specific labelled workspace.
Product Discovery
MVP Test Matrix
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan.When demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-75 min1-5 Tage1-5 Tage
Participantsdifferent
Scrum Team2-8NutzertrafficNutzertraffic
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Improvement actions, Team agreementsTest Matrix, Test PlanClick Data, Interest Signal, Learning DecisionInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
RetrospectiveImprovementLearning
ExperimentsValidationDiscoveryOptions
ValidationExperimentsDemandDiscovery
ValidationExperimentsDemandGrowth
Add more methods