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 a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
Paper illustration for NoEstimates.
Agile
NoEstimates
Paper illustration for Wideband Delphi.
Decision Making
Wideband Delphi
Paper illustration for Three-Point Estimation.
Decision Making
Three-Point Estimation
Purposedifferent
When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.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 opinion rarely holds up for planning when the future is genuinely uncertain. It separates options, evaluation criteria, and open risks. The result is captured as an Estimate Range, Assumption Log, and Expert Consensus Notes.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
Ongoinglaufend1-4 h or multiple rounds10-30 min je Item
Participantsdifferent
2-122-124-12 Experten1-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Kanban board, WIP policies, Flow metricsThroughput Data, Flow Forecast, Slicing RulesEstimate Range, Assumption Log, Expert Consensus NotesThree-Point Estimate, Risk Range, Assumption Notes
Tagsno overlap
FlowVisual managementDelivery
EstimationForecastingFlow
EstimationExpertsForecasting
EstimationUncertaintyForecasting
Add more methods