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 a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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.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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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
MediumHighMediumLow
Timedifferent
1-4 Wochen je Sprint, laufend1-4 h1-2 h45-90 min
Participantsdifferent
3-10 (Scrum Team)3-81-82-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalChallenge Findings, Risk Register, Mitigation PlanConcept Map, Relationship Labels, Knowledge GapsAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
AgileIterationCadence
RiskDecisionSensemaking
KnowledgeConceptsMappingSensemaking
AssumptionsRiskDecisionDiscovery
Add more methods