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 |  Facilitation Responsibility Poker |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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. | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 1-2 h | 45-90 min | 60–90 min |
Participantsdifferent | Team members involved | 4-12 | 3-10 | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Alignment Map, Open Issues, Decision Questions | Responsibility Map, Role Agreements, Open Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersStrategyFacilitation | RolesResponsibilityTeamFacilitation | StakeholdersAlignmentFacilitationChange |