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 for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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.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.
Complexitydifferent
MediumHighHighLow
Timedifferent
1-4 Wochen je Sprint, laufend0.5-3 Tage1-4 h20–45 min
Participantsdifferent
3-10 (Scrum Team)5-153-8Small cross-functional group
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalRich Picture, Root Definitions, Conceptual Models, Change AgendaChallenge Findings, Risk Register, Mitigation PlanRisk list, Mitigation plan, Assumption log
Tagsno overlap
AgileIterationCadence
Soft systemsComplexitySensemakingSystems thinking
RiskDecisionSensemaking
RiskDecisionFailurePlanning
Add more methods