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 Constraint Analysis.
Decision Making
Constraint Analysis
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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Purposedifferent
When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30-90 min3–4 h for initial assessment; preparation and deeper analysis additional1-3 Wochen vom Draft bis zur Entscheidung20–45 min
Participantsdifferent
2-81 or a small team; particularly suitable for 3–4 people3-20 ReviewerSmall cross-functional group
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Constraint List, Hard/Soft Classification, Option Impact Notes, Decision BoundariesLean 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 ticketsRisk list, Mitigation plan, Assumption log
Tagsno overlap
ConstraintsDecisionPlanningOptions
ArchitectureQualityRiskAssessmentLean
ArchitectureDecisionAsyncGovernance
RiskDecisionFailurePlanning
Add more methods