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 Open Space Technology.
Facilitation
Open Space Technology
Paper Kanban board with To Discuss, Discussing and Discussed columns, topic cards, votes and timer.
Facilitation
Lean Coffee
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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 a complex topic does not yet have a fitting agenda, Open Space Technology hands topic ownership back to the participants. The format suits questions that only move forward when real interest determines the order.When a group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait.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.
Complexitydifferent
MediumHighLowHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional0.5-2 Tage30-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people20-500+3-20Evaluation team, architects, and relevant stakeholders
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 checksSession Marketplace, Proceedings, Action TopicsPrioritized Topics, Discussion Notes, Action ItemsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
FacilitationLarge groupAutonomy
FacilitationAutonomyDialogue
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods