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 Iceberg Model | ![]() Systems Thinking Evaporating Cloud |
|---|---|---|---|
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 Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 30-60 min | 60-120 min |
Participantsdifferent | 3-10 (Scrum Team) | 2-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Iceberg Worksheet, Pattern Notes, Intervention Ideas | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments |
Tagsno overlap | AgileIterationCadence | Systems thinkingRoot causePatterns | Theory of ConstraintsAssumptionsSystems thinking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






