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
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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)
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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
30 min Setup, dann laufend2-6 h30-120 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-3 maintaining, briefing for everyone3-102-61 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceFMEA Table, Risk Priority, Mitigation ActionsObservation Notes, Improvement IdeasLean 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 checks
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskQualityOperationsRoot cause
LeanObservationProcessOperations
ArchitectureQualityRiskAssessmentLean
Add more methods