View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogLASR (Lightweight Approach for Software Reviews)Stakeholder Salience ModelROAM Board
| Criterion |  Delivery RAID Log |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Stakeholder Salience Model |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 3-15 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean | StakeholdersFacilitationAlignmentGovernance | RiskAgileTrackingAlignment |