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 Affinity Estimation.
Agile
Affinity Estimation
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Learning Review.
Operations
Learning Review
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
Purposedifferent
When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
30-90 min1-3 h1-3 h45–75 min
Participantsdifferent
3-123-103-10Team members involved
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsProcess Map, Handoff List, Improvement BacklogLearning Review Notes, System Factors, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
EstimationBacklogRelative sizing
ProcessOperationsImprovement
LearningRetrospectiveIncidentOperations
RetrospectiveLearningReflectionTeam
Add more methods