View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Systems Thinking Polarity Mapping |  Delivery Cost of Delay |  Agile WSJF |
|---|---|---|---|---|
Purposedifferent | 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. | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-2 h | 90-180 min | 45-90 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 3-12 | 3-8 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | 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 | Polarity Map, Warning Signs, Balance Actions | CoD Table, Prioritization Sequence | Ranked Backlog, Cost-of-Delay Assumptions |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | Systems thinkingTradeoffsLeadership | PrioritizationDeliveryEconomicsDecision | LeanEconomicsSequencePrioritization |