methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Three Amigos method illustration showing its working structure
Agile
Three Amigos
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 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.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
MediumLowHighLow
Timedifferent
1-2 h20-40 min pro StorySeveral meetings plus preparation and analysis; total effort depends on scope15-30 min
Participantsdifferent
3-123-6Evaluation team, architects, and relevant stakeholders3
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsAcceptance Criteria, Story UpdatePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsClarified Story, Test Examples, Open Questions
Tagsno overlap
Systems thinkingTradeoffsLeadership
AgileRequirementsRefinementBehavior-Driven Development
ArchitectureQualityRiskTradeoffsStakeholders
CollaborationBehavior-Driven DevelopmentQualityRefinement
Add more methods