View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Facilitation Alignment Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 45–75 min | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min |
Participantsdifferent | Team members involved | 4-12 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Alignment Map, Open Issues, Decision Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Emotion Board, Themes, Action Items |
Tagsno overlap | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersStrategyFacilitation | ArchitectureQualityRiskTradeoffsStakeholders | RetrospectiveTeamReflection |