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.

Selected:Example MappingRAID LogContext CanvasATAM (Architecture Tradeoff Analysis Method)
Criterion
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.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
30-60 min30 min Setup, dann laufend45-90 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-71-3 maintaining, briefing for everyone3-10Evaluation team, architects, and relevant stakeholders
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Example Map, Acceptance Criteria, Open QuestionsRAID Log, Status Report SourceContext canvas, Open questions, Shared context notesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Behavior-Driven DevelopmentRequirementsExamplesRefinement
RiskTrackingStakeholdersGovernance
ContextFramingRequirementsCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods