View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Polarity MappingSpecification by ExampleAcceptance Criteria WorkshopATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Systems Thinking Polarity Mapping |  Agile Specification by Example |  Agile Acceptance Criteria Workshop |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 | 1-2 h | 60-90 min pro Feature | 20-40 min pro Story | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 3-6 | 3-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | Example Table, Acceptance Tests | 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 | Systems thinkingTradeoffsLeadership | AgileRequirementsExamplesBehavior-Driven Development | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureQualityRiskTradeoffsStakeholders |