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 Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
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)
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
60-90 min30 min Setup, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional1-2 h
Participantsdifferent
3-61-3 maintaining, briefing for everyone1 or a small team; particularly suitable for 3–4 people4-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Salience Diagram, Strategy per ClassRAID 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 checksAlignment Map, Open Issues, Decision Questions
Tagsno overlap
StakeholdersFacilitationAlignmentGovernance
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskAssessmentLean
AlignmentStakeholdersStrategyFacilitation
Add more methods