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
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
Paper illustration of a MoSCoW board with four columns and a visible release boundary.
Delivery
MoSCoW
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 of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Purposedifferent
When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-2 Tage30-90 min3–4 h for initial assessment; preparation and deeper analysis additional45-90 min
Participantsdifferent
10-503-121 or a small team; particularly suitable for 3–4 people2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Kano Matrix, Feature Classes, Priority ThemesPrioritized Backlog, Release Scope, Tradeoff NotesLean 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 checksAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
SatisfactionPrioritizationCustomer
PrioritizationScopeDecision
ArchitectureQualityRiskAssessmentLean
AssumptionsRiskDecisionDiscovery
Add more methods