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
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Fake Door Test
Product Discovery
Fake Door 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.The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible.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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.
Complexitydifferent
LowLowMediumMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter25-40 min1-3 h1-5 Tage
Participantsdifferent
Scrum Team1-53-10Nutzertraffic
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Improvement actions, Team agreementsLearning Card with evidence and next actionLearning Review Notes, System Factors, Improvement ActionsClick Data, Interest Signal, Learning Decision
Tagsno overlap
RetrospectiveImprovementLearning
ExperimentsValidationDiscoveryLearning
LearningRetrospectiveIncidentOperations
ValidationExperimentsDemandDiscovery
Add more methods