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 Standard Work Analysis.
Operations
Standard Work Analysis
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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
When the same task is done differently depending on the person, the method exposes the reliable core. It creates comparability without unnecessarily choking off needed latitude.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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
MediumLowLowMedium
Timedifferent
1-3 h30 min Setup, dann laufend45-90 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-61-3 maintaining, briefing for everyone2-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Standard Work Sheet, Deviation List, Improved Standard, Training NeedsRAID Log, Status Report SourceAssumption List, Critical Assumptions, Learning PlanLean 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
LeanProcessQuality
RiskTrackingStakeholdersGovernance
AssumptionsRiskDecisionDiscovery
ArchitectureQualityRiskAssessmentLean
Add more methods