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
Paper illustration for Responsibility Poker.
Facilitation
Responsibility Poker
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)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Accountability Ladder
Operations
Accountability Ladder
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.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
LowMediumLowLow
Timedifferent
45-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage20-45 min
Participantsdifferent
3-101 or a small team; particularly suitable for 3–4 people1-41-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Responsibility Map, Role Agreements, Open QuestionsLean 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 checksArchitecture Document, Context View, Runtime View, Deployment ViewOwnership Reflection, Action Commitment, Coaching Notes
Tagsno overlap
RolesResponsibilityTeamFacilitation
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
ResponsibilityLeadershipTeam
Add more methods