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 |  Facilitation Expectation Mapping |  Team Design Team Topologies Interaction Modes |  Facilitation Team Charter |
|---|---|---|---|---|
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 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 teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 45-90 min | Half day | 2-4 h |
Participantsdifferent | 3-6 | 3-12 | Team-Leads plus Architecture | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Expectation Map, Alignment Notes, Agreements | Interaction Heat Map, Agreements per Pair | Team Charter, Working Norms, Role Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | AlignmentStakeholdersTeam | TeamAlignmentCollaborationOrganization | TeamAlignmentCollaboration |