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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process.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.
Complexitysame
LowLowLowLow
Timedifferent
30-60 min30 min Setup, dann laufend15-30 min20-40 min initial, dann laufend
Participantsdifferent
3-71-3 maintaining, briefing for everyone33-15
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsRAID Log, Status Report SourceClarified Story, Test Examples, Open QuestionsROAM Board, Owner List
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskTrackingStakeholdersGovernance
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskAgileTrackingAlignment
Add more methods