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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Monte Carlo Forecasting.
Delivery
Monte Carlo Forecasting
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)
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Purposedifferent
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication.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 delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.
Complexitydifferent
LowHighMediumMedium
Timedifferent
5-20 min30-90 min Setup, danach laufend3–4 h for initial assessment; preparation and deeper analysis additional1-3 h
Participantsdifferent
3-201-81 or a small team; particularly suitable for 3–4 people4-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsForecast Percentiles, Throughput Dataset, Risk CommunicationLean 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 checksCurrent-state map, Future-state map, Bottleneck list
Tagsno overlap
EstimationEffortRisk
ForecastingFlowDelivery
ArchitectureQualityRiskAssessmentLean
LeanFlowWasteDelivery
Add more methods