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 |  Systems Thinking Intervention Mapping |  Systems Thinking Evaporating Cloud |  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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | High | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 1-5 Tage | 60-120 min | 2-5 min je Item |
Participantsdifferent | 3-9 | 4-12 | 2-8 | 3-9 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationAgileMeasurement | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | EstimationAgileRelative sizingTeam |