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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
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 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.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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-4 Wochen je Sprint, laufend15-60 min je Zyklus45-90 min2-4 h
Participantsdifferent
3-10 (Scrum Team)1-83-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Product Backlog, Sprint Backlog, Increment, Sprint GoalSituation Assessment, Decision Loop, Action UpdatesForce Field Map, Change Levers, Risk Notes7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
AgileIterationCadence
DecisionChangeLearningStrategy
ChangeDecisionStrategy
OrganizationStrategyAlignmentChange
Add more methods