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 of a horizontal story map with an activity backbone, task cards below it and a cross-map release line.
Product Discovery
User Story Mapping
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration of Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
When user goals and delivery scope could drift apart, it orders the journey from goal to slice. It makes visible where an MVP can genuinely be cut.When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2-4 h30-60 min6 Wochen Cycle + 2 Wochen Cool-Down10-20 min daily
Participantsdifferent
4-102-62-4 pro Pitch1
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Story Map, Release Slices, Backlog CandidatesSmaller Stories, Acceptance Criteria, Split RationalePitches, Bet-table decisions, Hill charts, Cooldown outcomesDaily Plan, Time Estimates, Review Notes
Tagsno overlap
BacklogJourneyPlanningMVP
BacklogIterationDelivery
PlanningDeliveryAutonomy
PlanningTime managementProductivityOperations
Add more methods