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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
Paper illustration of Shape Up with its method-specific working model.
Delivery
Shape Up
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)
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Purposedifferent
When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
1-2 h6 Wochen Cycle + 2 Wochen Cool-Down3–4 h for initial assessment; preparation and deeper analysis additional20–45 min
Participantsdifferent
2-102-4 pro Pitch1 or a small team; particularly suitable for 3–4 peopleSmall cross-functional group
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Radar Map, Capability Scores, Action AreasPitches, Bet-table decisions, Hill charts, Cooldown outcomesLean 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 checksRisk list, Mitigation plan, Assumption log
Tagsno overlap
AssessmentPortfolioCapability
PlanningDeliveryAutonomy
ArchitectureQualityRiskAssessmentLean
RiskDecisionFailurePlanning
Add more methods