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
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
Paper illustration for Ideal Days.
Agile
Ideal Days
Paper illustration for Planning Poker.
Agile
Planning Poker
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.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
MediumLowLowLow
Timedifferent
laufend1 h bis mehrere Wochen15-60 min2-5 min je Item
Participantsdifferent
2-121-82-93-9
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesPDCA Log, Experiment Plan, Learning Outcome, Standard ChangeIdeal Day Estimates, Assumption Notes, Capacity CaveatsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
EstimationForecastingFlow
Continuous improvementLeanExperiments
EstimationEffortAgile
EstimationAgileRelative sizingTeam
Add more methods