View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Responsibility PokerExpectation MappingLASR (Lightweight Approach for Software Reviews)Stakeholder Mapping
| Criterion |  Facilitation Responsibility Poker |  Facilitation Expectation Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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 | Low | Medium | Low |
Timedifferent | 45-90 min | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60–90 min |
Participantsdifferent | 3-10 | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Expectation Map, Alignment Notes, Agreements | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RolesResponsibilityTeamFacilitation | AlignmentStakeholdersTeam | ArchitectureQualityRiskAssessmentLean | StakeholdersAlignmentFacilitationChange |