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 Ideal Days |  Facilitation Team Charter |  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 effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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 collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 15-60 min | 2-4 h | 45-90 min |
Participantsdifferent | 3-9 | 2-9 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Team Charter, Working Norms, Role Notes | Working Agreements, Team Norms, Review Cadence |
Tagsno overlap | EstimationAgileMeasurement | EstimationEffortAgile | TeamAlignmentCollaboration | TeamCollaborationAgile |