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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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
LowLowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-90 min15-60 min je Zyklus
Participantsdifferent
Scrum Team2-81-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Improvement actions, Team agreementsAssumption List, Critical Assumptions, Learning PlanSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
RetrospectiveImprovementLearning
AssumptionsRiskDecisionDiscovery
DecisionChangeLearningStrategy
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review