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 Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-Down45-120 min1-3 Wochen vom Draft bis zur EntscheidungPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-4 pro Pitch2-63-20 ReviewerArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesChange Matrix, Cause Hypotheses, Validation Questions, Action ListRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
PlanningDeliveryAutonomy
ChangeRoot causeTroubleshootingComparison
ArchitectureDecisionAsyncGovernance
ArchitectureChangeAnalysisComparisonQuality
Add more methods