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 Learning Review.
Operations
Learning Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Purposedifferent
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 is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.
Complexitydifferent
MediumLowMedium
Timedifferent
1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorterOngoing
Participantsdifferent
3-10Scrum Team2-20
Formatdifferent
WorkshopWorkshopWorkshop + async
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreementsChat Transcript, Action Log, Automations
Tagsno overlap
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
CollaborationEngineeringIncident
Add more methods

Often compared together

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

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action 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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem