methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Scrum with its method-specific working model.
Agile
Scrum
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
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 Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
1-4 Wochen je Sprint, laufend1-3 h1-3 h2-4 h
Participantsdifferent
3-10 (Scrum Team)3-122-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalSystem Map, Dependencies, Leverage PointsCausal Loop Diagram, Feedback Notes, Leverage PointsFuture Reality Tree, Negative Branches, Assumption List, Improved Injections
Tagsno overlap
AgileIterationCadence
Systems thinkingMappingBoundariesChange
FeedbackSystems thinkingCausalityDynamics
Theory of ConstraintsSystems thinkingChange
Add more methods