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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
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.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 team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
30-90 min2–4 h review as a planning range; preparation and evaluation additional45-90 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
3-12Designers, developers as users, and facilitation4-12Scrum Team
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Postmortem Doc, Action Items, TimelinePrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSailboat Board, Risks, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
Site Reliability EngineeringIncidentLearningReliability
ArchitectureEngineeringFeedbackValidationTasks
RetrospectiveTeamImprovement
RetrospectiveImprovementLearning
Add more methods