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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Three Amigos method illustration showing its working structure
Agile
Three Amigos
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30-60 minOngoing15-30 min1-3 h
Participantsdifferent
3-72-2032-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsChat Transcript, Action Log, AutomationsClarified Story, Test Examples, Open QuestionsCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
CollaborationEngineeringIncident
CollaborationBehavior-Driven DevelopmentQualityRefinement
Root causeTreeIncidentQuality
Add more methods