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
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)
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Purposedifferent
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.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.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-3 Tage3–4 h for initial assessment; preparation and deeper analysis additional60-90 min30-60 min
Participantsdifferent
1-41 or a small team; particularly suitable for 3–4 people3-62-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture 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 checksSalience Diagram, Strategy per ClassPower Interest Grid, Strategy per Stakeholder
Tagsno overlap
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskAssessmentLean
StakeholdersFacilitationAlignmentGovernance
StakeholdersFacilitationAlignmentPlanning
Add more methods