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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufend2-8 h60-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone5-124-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsProblem Cluster, Prioritized Challenge, ExperimentPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskTrackingStakeholdersGovernance
Domain-Driven DesignEventsDiscoveryWorkshop
FacilitationDecisionProblem solvingWorkshop
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods