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 |  Team Design Team API |  Agile Planning Poker |  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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 | Low | Medium |
Timedifferent | 45-90 min | Half day initial, dann laufend | 2-5 min je Item | Half day |
Participantsdifferent | 3-12 | Ein Team plus Stakeholder | 3-9 | Team-Leads plus Architecture |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Team API Document | Relative Estimates, Assumption Notes, Split Candidates | Interaction Heat Map, Agreements per Pair |
Tags1 shared | TeamCollaborationAgile | TeamAlignmentCommunicationService | EstimationAgileRelative sizingTeam | TeamAlignmentCollaborationOrganization |