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 RAPID
Decision Making
RAPID
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.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.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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
45-90 min90-180 min1-3 Wochen vom Draft bis zur Entscheidung15-45 min
Participantsdifferent
3-123-63-20 Reviewer1-3
Formatdifferent
Workshop + asyncWorkshopAsyncAsync
Outputdifferent
RAPID Role Map, Recommendation, Decision LogGQM Table, Metric ProfilesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsADR File, Decision Log, Rationale
Tagsno overlap
DecisionRolesGovernance
MetricsMeasurementEngineeringAlignment
ArchitectureDecisionAsyncGovernance
ArchitectureRationaleDocumentationGovernance
Add more methods