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
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.
Complexitydifferent
LowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-60 min
Participantsdifferent
Scrum Team2-8
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Improvement actions, Team agreementsAssumption map, Test backlog, Risk ranking
Tagsno overlap
RetrospectiveImprovementLearning
AssumptionsRiskExperimentsValidation
Add more methods

Often compared together

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

Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective