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
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Argument Mapping
Decision Making
Argument 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.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.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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
MediumHighLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend1-4 h45-90 min1-3 h
Participantsdifferent
3-10 (Scrum Team)3-82-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalChallenge Findings, Risk Register, Mitigation PlanAssumption List, Critical Assumptions, Learning PlanArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
AgileIterationCadence
RiskDecisionSensemaking
AssumptionsRiskDecisionDiscovery
SensemakingDecisionRationale
Add more methods