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 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 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 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
15-30 min30 min Setup, dann laufend30-60 min30-60 min
Participantsdifferent
31-3 maintaining, briefing for everyone2-83-7
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop
Outputdifferent
Clarified Story, Test Examples, Open QuestionsRAID Log, Status Report SourceFishbone Diagram, Cause Categories, Investigation BacklogExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
RiskTrackingStakeholdersGovernance
Root causeQualityOperations
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods