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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter20-45 min
Participantsdifferent
Designers, developers as users, and facilitation3-10Scrum Team3-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLearning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreementsLessons learned, Action items, Event summary
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
LearningOperationsImprovement
Add more methods