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
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 Ideal Days.
Agile
Ideal Days
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Planning Poker.
Agile
Planning Poker
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.When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.
Complexitydifferent
MediumLowLowLow
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional15-60 min5-20 min2-5 min je Item
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-93-203-9
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
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 checksIdeal Day Estimates, Assumption Notes, Capacity CaveatsEffort Heatmap, Risk Signals, Discussion TargetsRelative Estimates, Assumption Notes, Split Candidates
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
EstimationEffortAgile
EstimationEffortRisk
EstimationAgileRelative sizingTeam
Add more methods