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 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 of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
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.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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.
Complexitysame
LowLowLowLow
Timedifferent
15-30 min20-40 min initial, dann laufend30 min Setup, dann laufend20-40 min pro Story
Participantsdifferent
33-151-3 maintaining, briefing for everyone3-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Clarified Story, Test Examples, Open QuestionsROAM Board, Owner ListRAID Log, Status Report SourceAcceptance Criteria, Story Update
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
AgileRequirementsRefinementBehavior-Driven Development
Add more methods