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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend45-90 min45-90 min15-60 min je Zyklus
Participantsdifferent
3-10 (Scrum Team)3-122-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalForce Field Map, Change Levers, Risk NotesAssumption List, Critical Assumptions, Learning PlanSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
AgileIterationCadence
ChangeDecisionStrategy
AssumptionsRiskDecisionDiscovery
DecisionChangeLearningStrategy
Add more methods