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
Paper illustration for Communication Plan
Delivery
Communication Plan
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
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 many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-4 h45-90 min6 Wochen Cycle + 2 Wochen Cool-Down30-60 min
Participantsdifferent
4-102-62-4 pro Pitch2-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Story Map, Release Slices, Backlog CandidatesCommunication Plan, Channel Matrix, Message CadencePitches, Bet-table decisions, Hill charts, Cooldown outcomesSmaller Stories, Acceptance Criteria, Split Rationale
Tagsno overlap
BacklogJourneyPlanningMVP
CommunicationStakeholdersDeliveryPlanning
PlanningDeliveryAutonomy
BacklogIterationDelivery
Add more methods