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 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)
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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
LowMediumHighLow
Timedifferent
30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional4-5 Tage15-45 min
Participantsdifferent
1-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people5-81-3
Formatdifferent
AsyncWorkshop + asyncWorkshopAsync
Outputdifferent
RAID 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 checksPrototype, Test Findings, Decision RationaleADR File, Decision Log, Rationale
Tagsno overlap
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
Design sprintPrototypeValidationInnovation
ArchitectureRationaleDocumentationGovernance
Add more methods