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
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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung3–4 h for initial assessment; preparation and deeper analysis additional30 min Setup, dann laufend60-120 min
Participantsdifferent
3-20 Reviewer1 or a small team; particularly suitable for 3–4 people1-3 maintaining, briefing for everyone2-8
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsLean 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 checksRAID Log, Status Report SourceCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ArchitectureQualityRiskAssessmentLean
RiskTrackingStakeholdersGovernance
ArchitectureCommunicationStakeholdersCanvas
Add more methods