View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Team Design Spotify Model Mapping | ![]() Decision Making Decision Rights Mapping | ![]() Agile Specification by Example | ![]() Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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 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 | Medium | Medium | Low |
Timedifferent | 90-180 min | 90-180 min | 60-90 min pro Feature | 30-60 min |
Participantsdifferent | 5-15 | 4-12 | 3-6 | 3-7 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Decision Rights Matrix, Agreement | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | DecisionGovernanceAlignmentResponsibility | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |



