View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Consensus WorkshopRAID LogLASR (Lightweight Approach for Software Reviews)Stakeholder Salience Model
| Criterion | ![]() Facilitation Consensus Workshop | ![]() Delivery RAID Log | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min |
Participantsdifferent | 5-30 | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Consensus Clusters, Theme Titles, Priority Areas | RAID Log, Status Report Source | Lean 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 | Salience Diagram, Strategy per Class |
Tagsno overlap | FacilitationConsensusWorkshopAlignment | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean | StakeholdersFacilitationAlignmentGovernance |



