View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Communication CanvasLASR (Lightweight Approach for Software Reviews)Acceptance Criteria WorkshopATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture Architecture Communication Canvas |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Acceptance Criteria Workshop |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 | Medium | Medium | Low | High |
Timedifferent | 60-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 20-40 min pro Story | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | 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 | Acceptance Criteria, Story Update | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | ArchitectureQualityRiskAssessmentLean | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureQualityRiskTradeoffsStakeholders |