View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Team CharterLASR (Lightweight Approach for Software Reviews)Team Topologies Interaction Modes
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Team Charter |  Architecture LASR (Lightweight Approach for Software Reviews) |  Team Design Team Topologies Interaction Modes |
|---|---|---|---|---|
Purposedifferent | 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. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional | Half day |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-12 | 1 or a small team; particularly suitable for 3–4 people | Team-Leads plus Architecture |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Team Charter, Working Norms, Role Notes | 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 | Interaction Heat Map, Agreements per Pair |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | TeamAlignmentCollaboration | ArchitectureQualityRiskAssessmentLean | TeamAlignmentCollaborationOrganization |