View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Dot EstimationAcceptance Criteria WorkshopFailure Mode and Effects AnalysisSpecification by Example
| Criterion |  Facilitation Dot Estimation |  Agile Acceptance Criteria Workshop |  Operations Failure Mode and Effects Analysis |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. |
Complexitydifferent | Low | Low | High | Medium |
Timedifferent | 5-20 min | 20-40 min pro Story | 2-6 h | 60-90 min pro Feature |
Participantsdifferent | 3-20 | 3-6 | 3-10 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Effort Heatmap, Risk Signals, Discussion Targets | Acceptance Criteria, Story Update | FMEA Table, Risk Priority, Mitigation Actions | Example Table, Acceptance Tests |
Tagsno overlap | EstimationEffortRisk | AgileRequirementsRefinementBehavior-Driven Development | RiskQualityOperationsRoot cause | AgileRequirementsExamplesBehavior-Driven Development |