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
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
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
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.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.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend20–45 min45-60 min30-90 min
Participantsdifferent
3-10 (Scrum Team)Small cross-functional group2-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalRisk list, Mitigation plan, Assumption logAssumption map, Test backlog, Risk rankingConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
AgileIterationCadence
RiskDecisionFailurePlanning
AssumptionsRiskExperimentsValidation
ConstraintsDecisionPlanningOptions
Add more methods