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 for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.
Complexitydifferent
LowHighLowMedium
Timedifferent
45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope15-45 min1-3 Tage
Participantsdifferent
3-10Evaluation team, architects, and relevant stakeholders1-31-4
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsADR File, Decision Log, RationaleArchitecture Views, Cross-view Notes, Rationale
Tagsno overlap
AutonomyRolesTeam
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureRationaleDocumentationGovernance
DocumentationStakeholdersArchitecture
Add more methods