View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Open Space TechnologyATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)Barcamp
| Criterion |  Facilitation Open Space Technology |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Barcamp |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. |
Complexitydifferent | High | High | Medium | Medium |
Timedifferent | 0.5-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | Halber Tag bis 2 Tage |
Participantsdifferent | 20-500+ | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 15-200 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Session Marketplace, Proceedings, Action Topics | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 checks | Session Board, Session Notes, Community Learnings |
Tagsno overlap | FacilitationLarge groupAutonomy | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | FacilitationLarge groupLearning |