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 PERT Estimation.
Decision Making
PERT Estimation
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for NoEstimates.
Agile
NoEstimates
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
15-45 min45-120 minlaufend2-6 h
Participantsdifferent
1-82-62-123-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
PERT Estimate, Expected Value, Risk NotesChange Matrix, Cause Hypotheses, Validation Questions, Action ListThroughput Data, Flow Forecast, Slicing RulesFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
EstimationUncertaintyRisk
ChangeRoot causeTroubleshootingComparison
EstimationForecastingFlow
RiskRoot causeSafety
Add more methods