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 Story Points |  Agile Working Agreements |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
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 teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | laufend, 1-5 min je Item | 45-90 min | Half day |
Participantsdifferent | 2-12 | 3-9 | 3-12 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | Point Estimates, Reference Stories, Velocity Data | Working Agreements, Team Norms, Review Cadence | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | EstimationAgileRoadmap | EstimationAgileMeasurement | TeamCollaborationAgile | TeamAlignmentCollaborationOrganization |