View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Mode and Effects AnalysisSpecification by ExampleCompetency QuestionsAcceptance Criteria Workshop
| Criterion |  Operations Failure Mode and Effects Analysis |  Agile Specification by Example |  Knowledge Modeling Competency Questions |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 2-6 h | 60-90 min pro Feature | 2-4 h | 20-40 min pro Story |
Participantsdifferent | 3-10 | 3-6 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | FMEA Table, Risk Priority, Mitigation Actions | Example Table, Acceptance Tests | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Acceptance Criteria, Story Update |
Tagsno overlap | RiskQualityOperationsRoot cause | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsRefinementBehavior-Driven Development |