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 |  Delivery RAID Log |  Facilitation Alignment Mapping |  Agile Example Mapping |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 30 min Setup, dann laufend | 1-2 h | 30-60 min |
Participantsdifferent | 3-6 | 1-3 maintaining, briefing for everyone | 4-12 | 3-7 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation | Behavior-Driven DevelopmentRequirementsExamplesRefinement |