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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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 capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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-2 h30 min Setup, dann laufend1-2 Tage3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-101-3 maintaining, briefing for everyone1-41 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Radar Map, Capability Scores, Action AreasRAID Log, Status Report SourceArchitecture Document, Context View, Runtime View, Deployment ViewLean 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
AssessmentPortfolioCapability
RiskTrackingStakeholdersGovernance
ArchitectureDocumentationCommunication
ArchitectureQualityRiskAssessmentLean
Add more methods