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 |  Facilitation Team Charter |  Agile Planning Poker |  Agile Working Agreements |
|---|---|---|---|---|
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 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. | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | laufend, 1-5 min je Item | 2-4 h | 2-5 min je Item | 45-90 min |
Participantsdifferent | 3-9 | 3-12 | 3-9 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Team Charter, Working Norms, Role Notes | Relative Estimates, Assumption Notes, Split Candidates | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | EstimationAgileMeasurement | TeamAlignmentCollaboration | EstimationAgileRelative sizingTeam | TeamCollaborationAgile |