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 Scrum |  Agile Three Amigos |  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 a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend | 15-30 min | 45-90 min |
Participantsdifferent | 3-6 | 3-10 (Scrum Team) | 3 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Clarified Story, Test Examples, Open Questions | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence | CollaborationBehavior-Driven DevelopmentQualityRefinement | TeamCollaborationAgile |