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 a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of a Lean Canvas with nine fields, notes, and one highlighted learning risk.
Product Strategy
Lean Canvas
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable.The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible.
Complexitydifferent
LowMediumMediumLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-60 min45-90 min25-40 min
Participantsdifferent
Scrum Team2-81-61-5
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Improvement actions, Team agreementsAssumption map, Test backlog, Risk rankingLean Canvas, Core Assumptions, Experiment BacklogLearning Card with evidence and next action
Tagsno overlap
RetrospectiveImprovementLearning
AssumptionsRiskExperimentsValidation
StartupLeanAssumptionsBusiness model
ExperimentsValidationDiscoveryLearning
Add more methods