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 for Constraint Analysis.
Decision Making
Constraint Analysis
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumLowLowHigh
Timedifferent
1-4 Wochen je Sprint, laufend20–45 min30-90 min1-4 h
Participantsdifferent
3-10 (Scrum Team)Small cross-functional group2-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalRisk list, Mitigation plan, Assumption logConstraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
AgileIterationCadence
RiskDecisionFailurePlanning
ConstraintsDecisionPlanningOptions
RiskDecisionSensemaking
Add more methods