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.

Selected:ARID (Active Reviews for Intermediate Designs)After-Action ReviewSprint Retrospective4Ls Retrospective
Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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
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 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.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.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
MediumLowLowLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional20-45 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45–75 min
Participantsdifferent
Designers, developers as users, and facilitation3-12Scrum TeamTeam members involved
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsLessons learned, Action items, Event summaryImprovement actions, Team agreements4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
LearningOperationsImprovement
RetrospectiveImprovementLearning
RetrospectiveLearningReflectionTeam
Add more methods