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 review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for NoEstimates.
Agile
NoEstimates
Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Purposedifferent
After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
LowMediumHighMedium
Timedifferent
20-45 minlaufend30-90 min Setup, danach laufend1-3 h
Participantsdifferent
3-122-121-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Lessons learned, Action items, Event summaryThroughput Data, Flow Forecast, Slicing RulesForecast Percentiles, Throughput Dataset, Risk CommunicationProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
LearningOperationsImprovement
EstimationForecastingFlow
ForecastingFlowDelivery
ProcessOperationsImprovement
Add more methods