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:Process MappingARID (Active Reviews for Intermediate Designs)Sprint Retrospective4Ls Retrospective
Criterion
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
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.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.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
MediumMediumLowLow
Timedifferent
1-3 h2–4 h review as a planning range; preparation and evaluation additionalUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45–75 min
Participantsdifferent
3-10Designers, developers as users, and facilitationScrum TeamTeam members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsImprovement actions, Team agreements4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ProcessOperationsImprovement
ArchitectureEngineeringFeedbackValidationTasks
RetrospectiveImprovementLearning
RetrospectiveLearningReflectionTeam
Add more methods