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
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.
Complexitysame
LowLowLow
Timedifferent
20-40 min initial, dann laufend45-90 min30-60 min
Participantsdifferent
3-153-123-7
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
ROAM Board, Owner ListExpectation Map, Alignment Notes, AgreementsExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods

Often compared together

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

Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping