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
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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 team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend45-90 min20–45 min45-60 min
Participantsdifferent
3-10 (Scrum Team)2-8Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalAssumption List, Critical Assumptions, Learning PlanRisk list, Mitigation plan, Assumption logAssumption map, Test backlog, Risk ranking
Tagsno overlap
AgileIterationCadence
AssumptionsRiskDecisionDiscovery
RiskDecisionFailurePlanning
AssumptionsRiskExperimentsValidation
Add more methods