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
Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration of Lean Startup with its method-specific working model.
Innovation
Lean Startup
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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
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.For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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
MediumMediumHighLow
Timedifferent
1-3 hWochen bis Monate je LernzyklusSeveral meetings plus preparation and analysis; total effort depends on scope45–75 min
Participantsdifferent
3-102-8Evaluation team, architects, and relevant stakeholdersTeam members involved
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Learning Review Notes, System Factors, Improvement ActionsHypothesis list, MVPs, Learning reports, Pivot or persevere decisionPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
LearningRetrospectiveIncidentOperations
LeanStartupValidationMVP
ArchitectureQualityRiskTradeoffsStakeholders
RetrospectiveLearningReflectionTeam
Add more methods