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
Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
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 for Dot Estimation.
Facilitation
Dot Estimation
Purposedifferent
On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes.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
MediumMediumMediumLow
Timedifferent
15-45 minOngoing3–4 h for initial assessment; preparation and deeper analysis additional5-20 min
Participantsdifferent
1-82-121 or a small team; particularly suitable for 3–4 people3-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
PERT Estimate, Expected Value, Risk NotesKanban board, WIP policies, Flow metricsLean 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 checksEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationUncertaintyRisk
FlowVisual managementDelivery
ArchitectureQualityRiskAssessmentLean
EstimationEffortRisk
Add more methods