View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Agile Acceptance Criteria Workshop |  Delivery RAID Log |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 20-40 min pro Story | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 3-12 | 3-6 | 1-3 maintaining, briefing for everyone | 3-7 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Acceptance Criteria, Story Update | RAID Log, Status Report Source | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AlignmentStakeholdersTeam | AgileRequirementsRefinementBehavior-Driven Development | RiskTrackingStakeholdersGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement |