View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Dot Estimation |
|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | Ongoing | 3–4 h for initial assessment; preparation and deeper analysis additional | 5-20 min |
Participantsdifferent | 2-12 | 1 or a small team; particularly suitable for 3–4 people | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | 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 | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureQualityRiskAssessmentLean | EstimationEffortRisk |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
