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 Team Topologies Interaction Modes |  Agile Example Mapping |  Facilitation Team Charter |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | Half day | 30-60 min | 2-4 h | 60-90 min pro Feature |
Participantsdifferent | Team-Leads plus Architecture | 3-7 | 3-12 | 3-6 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | Example Map, Acceptance Criteria, Open Questions | Team Charter, Working Norms, Role Notes | Example Table, Acceptance Tests |
Tagsno overlap | TeamAlignmentCollaborationOrganization | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamAlignmentCollaboration | AgileRequirementsExamplesBehavior-Driven Development |