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 Example Mapping |  Agile Scrum |  Agile Three Amigos |
|---|---|---|---|---|
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 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min | 30-60 min | 1-4 Wochen je Sprint, laufend | 15-30 min |
Participantsdifferent | 2-6 | 3-7 | 3-10 (Scrum Team) | 3 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Example Map, Acceptance Criteria, Open Questions | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | BacklogIterationDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileIterationCadence | CollaborationBehavior-Driven DevelopmentQualityRefinement |