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
Paper illustration of DIBB with its method-specific working model.
Product Strategy
DIBB
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
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.DIBB helps clarify target groups, value, goals, and priorities by making the logic behind a decision explicit. It captures results as a DIBB document, belief list, bet list, and learning report.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.
Complexitydifferent
MediumLowLowHigh
Timedifferent
1-4 Wochen je Sprint, laufend1-2 h45-90 minHalf day
Participantsdifferent
3-10 (Scrum Team)2-83-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalDIBB document, Belief list, Bet list, Learning reportForce Field Map, Change Levers, Risk NotesLeverage Map, Action Strategy
Tagsno overlap
AgileIterationCadence
StrategyDecisionAssumptionsHypothesis
ChangeDecisionStrategy
Systems thinkingChangeStrategy
Add more methods