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 Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration for RAPID
Decision Making
RAPID
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.
Complexitydifferent
HighMediumLowMedium
Timedifferent
90-180 min45-90 min1-2 h1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
3-83-123-103-20 Reviewer
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
CoD Table, Prioritization SequenceRAPID Role Map, Recommendation, Decision LogArchitecture Canvas, Goals, Constraints, Quality AttributesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
PrioritizationDeliveryEconomicsDecision
DecisionRolesGovernance
CanvasArchitectureAlignmentWorkshop
ArchitectureDecisionAsyncGovernance
Add more methods