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 Shape Up with its method-specific working model.
Delivery
Shape Up
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration for Time Blocking
Operations
Time Blocking
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
Purposedifferent
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.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.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-Down30-60 min15-30 min Planung, laufend2-4 h
Participantsdifferent
2-4 pro Pitch2-614-10
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesSmaller Stories, Acceptance Criteria, Split RationaleBlocked Calendar, Capacity View, Focus PlanStory Map, Release Slices, Backlog Candidates
Tagsno overlap
PlanningDeliveryAutonomy
BacklogIterationDelivery
PlanningTime managementFocus
BacklogJourneyPlanningMVP
Add more methods