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 Three Amigos |  Agile Example Mapping |  Agile Working Agreements |
|---|---|---|---|---|
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 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. | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min pro Feature | 15-30 min | 30-60 min | 45-90 min |
Participantsdifferent | 3-6 | 3 | 3-7 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Clarified Story, Test Examples, Open Questions | Example Map, Acceptance Criteria, Open Questions | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamCollaborationAgile |