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 an IBIS map with issues, positions and arguments
Knowledge Modeling
IBIS
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus.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.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 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
MediumLowMediumMedium
Timedifferent
1-3 h30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
2-81-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people3-20 Reviewer
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Issue Map, Positions, Argument NotesRAID Log, Status Report SourceLean 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 checksRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
RationaleKnowledgeDecision
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
ArchitectureDecisionAsyncGovernance
Add more methods