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 Example Mapping |  Agile Scrum |  Agile Working Agreements |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | 1-4 Wochen je Sprint, laufend | 45-90 min | 20-40 min pro Story |
Participantsdifferent | 3-7 | 3-10 (Scrum Team) | 3-12 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Working Agreements, Team Norms, Review Cadence | Acceptance Criteria, Story Update |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileIterationCadence | TeamCollaborationAgile | AgileRequirementsRefinementBehavior-Driven Development |