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 for NoEstimates.
Agile
NoEstimates
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Anonymous individual judgments pass through feedback loops to form a distribution.
Decision Making
Delphi Method
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together.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
MediumMediumHighMedium
Timedifferent
laufend30-90 min1-4 Wochen15-60 min je Zyklus
Participantsdifferent
2-123-126-30 Experten1-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesPostmortem Doc, Action Items, TimelineExpert Forecast, Consensus Range, Assumption NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
EstimationForecastingFlow
Site Reliability EngineeringIncidentLearningReliability
ForecastingExpertsDecisionStrategy
DecisionChangeLearningStrategy
Add more methods