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 Working Agreements |  Agile ROAM Board |  Agile Specification by Example |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 20-40 min initial, dann laufend | 60-90 min pro Feature | Half day |
Participantsdifferent | 3-12 | 3-15 | 3-6 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | ROAM Board, Owner List | Example Table, Acceptance Tests | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | TeamCollaborationAgile | RiskAgileTrackingAlignment | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCollaborationOrganization |