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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitydifferent
MediumMediumLow
Timedifferent
laufend1-3 h30-60 min
Participantsdifferent
2-123-103-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Throughput Data, Flow Forecast, Slicing RulesProcess Map, Handoff List, Improvement BacklogStart Stop Continue Board, Improvement Actions
Tagsno overlap
EstimationForecastingFlow
ProcessOperationsImprovement
RetrospectiveImprovementTeamReflection
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective