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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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
MediumHighMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-4 h3–4 h for initial assessment; preparation and deeper analysis additional15-45 min
Participantsdifferent
3-20 Reviewer3-81 or a small team; particularly suitable for 3–4 people1-3
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsChallenge Findings, Risk Register, Mitigation PlanLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDecisionAsyncGovernance
RiskDecisionSensemaking
ArchitectureQualityRiskAssessmentLean
ArchitectureRationaleDocumentationGovernance
Add more methods