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
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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
Purposedifferent
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.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 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.
Complexitysame
LowLowLowLow
Timedifferent
15-30 min30 min Setup, dann laufend30-60 min20-40 min initial, dann laufend
Participantsdifferent
31-3 maintaining, briefing for everyone3-73-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Clarified Story, Test Examples, Open QuestionsRAID Log, Status Report SourceExample Map, Acceptance Criteria, Open QuestionsROAM Board, Owner List
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskTrackingStakeholdersGovernance
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskAgileTrackingAlignment
Add more methods