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 Story Points |  Agile T-Shirt Sizing |  Facilitation Team Charter |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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 effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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 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 | Medium | Low | Medium | Medium |
Timedifferent | laufend, 1-5 min je Item | 15-45 min | 2-4 h | Half day |
Participantsdifferent | 3-9 | 2-12 | 3-12 | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Size Buckets, Rough Backlog Map, Split Candidates | Team Charter, Working Norms, Role Notes | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | EstimationAgileMeasurement | EstimationAgileRoadmap | TeamAlignmentCollaboration | TeamAlignmentCollaborationOrganization |