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 Systems Mapping |  Systems Thinking Causal Loop Diagram |  Systems Thinking Stock and Flow Diagram |
|---|---|---|---|---|
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. | 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. | A Causal Loop Diagram makes feedback, reinforcement, and balance in a system legible. It uncovers side effects and self-reinforcement that stay hidden in linear explanations. | A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 1-3 h | 2-6 h |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 2-8 | 1-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | System Map, Dependencies, Leverage Points | Causal Loop Diagram, Feedback Notes, Leverage Points | Stock and Flow Model, Dynamics Notes, Simulation Hypotheses |
Tagsno overlap | AgileIterationCadence | Systems thinkingMappingBoundariesChange | FeedbackSystems thinkingCausalityDynamics | DynamicsSimulationFeedbackSystems thinking |