View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Specification by Example | ![]() Agile Example Mapping | ![]() Agile Three Amigos | ![]() Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 60-90 min pro Feature | 30-60 min | 15-30 min | 1-6 Wochen |
Participantsdifferent | 3-6 | 3-7 | 3 | 4-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Clarified Story, Test Examples, Open Questions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | CollaborationBehavior-Driven DevelopmentQualityRefinement | QualityProblem solvingRoot cause |



