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 Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional60-180 minSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people4-20Evaluation team, architects, and relevant stakeholders3-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
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 checksCynefin Map, Domain-specific Actions, Sensemaking NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ComplexitySensemakingDecision
ArchitectureQualityRiskTradeoffsStakeholders
RiskDecisionSensemaking
Add more methods