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 Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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 Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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 a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
LowHighMediumMedium
Timedifferent
45-90 min1-6 Wochen3–4 h for initial assessment; preparation and deeper analysis additional1-4 h
Participantsdifferent
3-104-101 or a small team; particularly suitable for 3–4 people3-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role Agreements8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanLean 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 checksProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
AutonomyRolesTeam
QualityProblem solvingRoot cause
ArchitectureQualityRiskAssessmentLean
Root causeProblem solvingQualityIncident
Add more methods