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
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects 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.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowLowLowHigh
Timedifferent
30-60 min5-20 min30-60 min2-6 h
Participantsdifferent
3-73-202-83-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsEffort Heatmap, Risk Signals, Discussion TargetsFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
EstimationEffortRisk
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods