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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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
Purposedifferent
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.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.
Complexitydifferent
LowMedium
Timedifferent
20-40 min initial, dann laufend2-8 h
Participantsdifferent
3-155-12
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListEvent Timeline, Ubiquitous Language, Boundaries, Open Questions
Tagsno overlap
RiskAgileTrackingAlignment
Domain-Driven DesignEventsDiscoveryWorkshop
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration of Dual Track Agile with its method-specific working model.
Product Discovery
Dual-Track Agile
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling