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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Three-Point Estimation.
Decision Making
Three-Point Estimation
Paper illustration for Future Reality Tree.
Systems Thinking
Future Reality Tree
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.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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.A Future Reality Tree shows how desired actions are meant to lead to a better system state. The method checks whether a path of change holds together logically before time flows into implementation.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
laufend1-3 h10-30 min je Item2-4 h
Participantsdifferent
2-123-121-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesSystem Map, Dependencies, Leverage PointsThree-Point Estimate, Risk Range, Assumption NotesFuture Reality Tree, Negative Branches, Assumption List, Improved Injections
Tagsno overlap
EstimationForecastingFlow
Systems thinkingMappingBoundariesChange
EstimationUncertaintyForecasting
Theory of ConstraintsSystems thinkingChange
Add more methods