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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
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 Learning Review.
Operations
Learning Review
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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
30-90 min30-90 min45–75 min1-3 h
Participantsdifferent
3-123-12Team members involved3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsPostmortem Doc, Action Items, Timeline4Ls Board, Learning Themes, Improvement ActionsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
EstimationBacklogRelative sizing
Site Reliability EngineeringIncidentLearningReliability
RetrospectiveLearningReflectionTeam
LearningRetrospectiveIncidentOperations
Add more methods