View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingFailure Mode and Effects AnalysisCompetency QuestionsSpecification by Example
| Criterion |  Agile Example Mapping |  Operations Failure Mode and Effects Analysis |  Knowledge Modeling Competency Questions |  Agile Specification by Example |
|---|---|---|---|---|
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 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. | 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 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 | High | Medium | Medium |
Timedifferent | 30-60 min | 2-6 h | 2-4 h | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 3-10 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | FMEA Table, Risk Priority, Mitigation Actions | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskQualityOperationsRoot cause | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development |