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
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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
60-90 min3–4 h for initial assessment; preparation and deeper analysis additional20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
3-61 or a small team; particularly suitable for 3–4 people3-151-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Salience Diagram, Strategy per ClassLean 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 checksROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
StakeholdersFacilitationAlignmentGovernance
ArchitectureQualityRiskAssessmentLean
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods