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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Paper illustration of Team API with its method-specific working model.
Team Design
Team API
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.When expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document.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
LowLowLowHigh
Timedifferent
20-40 min initial, dann laufend45-90 minHalf day initial, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-153-12Ein Team plus StakeholderEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListExpectation Map, Alignment Notes, AgreementsTeam API DocumentPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskAgileTrackingAlignment
AlignmentStakeholdersTeam
TeamAlignmentCommunicationService
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods