View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Standard Work Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Three Amigos |
|---|---|---|---|
Purposedifferent | When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude. | 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | 3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Standard Work Sheet, Deviation List, Improved Standard, Training Needs | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Clarified Story, Test Examples, Open Questions |
Tags1 shared | LeanProcessQuality | ArchitectureQualityRiskTradeoffsStakeholders | CollaborationBehavior-Driven DevelopmentQualityRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
