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 Expectation Mapping.
Facilitation
Expectation Mapping
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 illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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.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
LowMediumMediumLow
Timedifferent
45-90 min60-90 min3–4 h for initial assessment; preparation and deeper analysis additional30 min Setup, dann laufend
Participantsdifferent
3-123-61 or a small team; particularly suitable for 3–4 people1-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshopWorkshop + asyncAsync
Outputdifferent
Expectation Map, Alignment Notes, AgreementsSalience 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 checksRAID Log, Status Report Source
Tagsno overlap
AlignmentStakeholdersTeam
StakeholdersFacilitationAlignmentGovernance
ArchitectureQualityRiskAssessmentLean
RiskTrackingStakeholdersGovernance
Add more methods