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 |  Team Design Spotify Model Mapping |  Facilitation Expectation Mapping |  Facilitation Alignment 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. | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 90-180 min | 45-90 min | 1-2 h |
Participantsdifferent | 3-6 | 5-15 | 3-12 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Spotify Model Map, Action List | Expectation Map, Alignment Notes, Agreements | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | TeamOrganizationAlignmentDiagnosis | AlignmentStakeholdersTeam | AlignmentStakeholdersStrategyFacilitation |