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 |  Team Design Team API |  Facilitation Alignment Mapping |  Facilitation Power Interest Grid |
|---|---|---|---|---|
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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45–75 min | Half day initial, dann laufend | 1-2 h | 30-60 min |
Participantsdifferent | Team members involved | Ein Team plus Stakeholder | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Team API Document | Alignment Map, Open Issues, Decision Questions | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | RetrospectiveLearningReflectionTeam | TeamAlignmentCommunicationService | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentPlanning |