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 T-Shirt Sizing |  Agile Working Agreements |  Team Design Team Topologies Interaction Modes |  Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 45-90 min | Half day | 45-90 min |
Participantsdifferent | 2-12 | 3-12 | Team-Leads plus Architecture | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Working Agreements, Team Norms, Review Cadence | Interaction Heat Map, Agreements per Pair | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | EstimationAgileRoadmap | TeamCollaborationAgile | TeamAlignmentCollaborationOrganization | AlignmentStakeholdersTeam |