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 Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 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.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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowLowMediumMedium
Timedifferent
15-30 min20-40 min pro StoryOngoing1-4 h
Participantsdifferent
33-62-203-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Clarified Story, Test Examples, Open QuestionsAcceptance Criteria, Story UpdateChat Transcript, Action Log, AutomationsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
CollaborationBehavior-Driven DevelopmentQualityRefinement
AgileRequirementsRefinementBehavior-Driven Development
CollaborationEngineeringIncident
Root causeProblem solvingQualityIncident
Add more methods