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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-4 Wochen je Sprint, laufend20-40 min initial, dann laufend20–45 min45-90 min
Participantsdifferent
3-10 (Scrum Team)3-15Small cross-functional group2-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalROAM Board, Owner ListRisk list, Mitigation plan, Assumption logAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
AgileIterationCadence
RiskAgileTrackingAlignment
RiskDecisionFailurePlanning
AssumptionsRiskDecisionDiscovery
Add more methods