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 |  Agile Planning Poker |
|---|---|---|---|---|
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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 15-45 min | 2-4 h | 2-5 min je Item |
Participantsdifferent | 3-9 | 2-12 | 3-12 | 3-9 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Size Buckets, Rough Backlog Map, Split Candidates | Team Charter, Working Norms, Role Notes | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationAgileMeasurement | EstimationAgileRoadmap | TeamAlignmentCollaboration | EstimationAgileRelative sizingTeam |