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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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 calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Paper illustration of Riskiest Assumption Test with a method-specific labelled workspace.
Product Discovery
Riskiest Assumption Test
Purposedifferent
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.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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter2–4 h review as a planning range; preparation and evaluation additional45-60 min1-2 Wochen pro Iteration
Participantsdifferent
Scrum TeamDesigners, developers as users, and facilitation2-82-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Improvement actions, Team agreementsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAssumption map, Test backlog, Risk rankingPrioritized Assumption List, Test Plan, Results Report
Tagsno overlap
RetrospectiveImprovementLearning
ArchitectureEngineeringFeedbackValidationTasks
AssumptionsRiskExperimentsValidation
ExperimentsValidationDiscoveryAssumptions
Add more methods