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 Scrum |  Systems Thinking Evaporating Cloud |  Systems Thinking Systems Mapping |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 60-120 min | 1-3 h |
Participantsdifferent | 3-10 (Scrum Team) | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | System Map, Dependencies, Leverage Points |
Tagsno overlap | AgileIterationCadence | Theory of ConstraintsAssumptionsSystems thinking | Systems thinkingMappingBoundariesChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
