View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Agile Story Points |  Agile T-Shirt Sizing |
|---|---|---|---|
Purposedifferent | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-2 h | laufend, 1-5 min je Item | 15-45 min |
Participantsdifferent | 1-8 | 3-9 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Point Estimates, Reference Stories, Velocity Data | Size Buckets, Rough Backlog Map, Split Candidates |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | EstimationAgileMeasurement | EstimationAgileRoadmap |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
