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 DMAIC.
Operations
DMAIC
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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)
Purposedifferent
For a process problem with fluctuating performance, the method brings analysis and improvement into a disciplined sequence. It creates a framework in which numbers, causes, and control come together.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
HighLowLowMedium
Timedifferent
2-12 Wochen60-90 min45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
3-104-122-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Project Charter, Measurement Plan, Cause Analysis, Control PlanAnnotated Diagram, Prioritized Risk List, Action BacklogAssumption List, Critical Assumptions, Learning 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 checks
Tagsno overlap
Continuous improvementQualityProcess improvement
RiskArchitectureWorkshopValidation
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
Add more methods