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 a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowLowMedium
Timedifferent
30-60 min20-40 min initial, dann laufend30 min Setup, dann laufend1-2 h
Participantsdifferent
3-73-151-3 maintaining, briefing for everyone4-12
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsROAM Board, Owner ListRAID Log, Status Report SourceAlignment Map, Open Issues, Decision Questions
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
AlignmentStakeholdersStrategyFacilitation
Add more methods