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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for NoEstimates.
Agile
NoEstimates
Paper illustration for Three-Point Estimation.
Decision Making
Three-Point Estimation
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Purposedifferent
Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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.A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
30 min Setup, dann laufendlaufend10-30 min je Item15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone2-121-81-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceThroughput Data, Flow Forecast, Slicing RulesThree-Point Estimate, Risk Range, Assumption NotesPERT Estimate, Expected Value, Risk Notes
Tagsno overlap
RiskTrackingStakeholdersGovernance
EstimationForecastingFlow
EstimationUncertaintyForecasting
EstimationUncertaintyRisk
Add more methods