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 Story Splitting |  Agile Three Amigos |  Agile Specification by Example |  Agile Scrum |
|---|---|---|---|---|
Purposedifferent | When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min | 15-30 min | 60-90 min pro Feature | 1-4 Wochen je Sprint, laufend |
Participantsdifferent | 2-6 | 3 | 3-6 | 3-10 (Scrum Team) |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | Product Backlog, Sprint Backlog, Increment, Sprint Goal |
Tagsno overlap | BacklogIterationDelivery | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | AgileIterationCadence |