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
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 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 a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
LowLowLowLow
Timedifferent
20-40 min initial, dann laufend15-30 min30-60 min30-60 min
Participantsdifferent
3-1532-83-7
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
ROAM Board, Owner ListClarified Story, Test Examples, Open QuestionsFishbone Diagram, Cause Categories, Investigation BacklogExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
RiskAgileTrackingAlignment
CollaborationBehavior-Driven DevelopmentQualityRefinement
Root causeQualityOperations
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods