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
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
Purposedifferent
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 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 decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.
Complexitydifferent
MediumLowLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional45-90 min45-90 min20-45 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people3-103-101-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
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 checksResponsibility Map, Role Agreements, Open QuestionsDelegation Board, Decision Boundaries, Role AgreementsOwnership Reflection, Action Commitment, Coaching Notes
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
RolesResponsibilityTeamFacilitation
AutonomyRolesTeam
ResponsibilityLeadershipTeam
Add more methods