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 of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowLowMediumMedium
Timedifferent
30 min Setup, dann laufend30-60 min1-3 Tage3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
1-3 maintaining, briefing for everyone3-101-41 or a small team; particularly suitable for 3–4 people
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RAID Log, Status Report SourceRisk Matrix, Top Risk ListArchitecture Views, Cross-view Notes, RationaleLean 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
RiskDecisionPrioritizationAssessment
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskAssessmentLean
Add more methods