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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
A paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
Purposedifferent
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.Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.
Complexitydifferent
MediumHighHighMedium
Timedifferent
30-60 min90-180 min45-90 min1-3 h
Participantsdifferent
2-63-83-104-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleCoD Table, Prioritization SequenceRanked Backlog, Cost-of-Delay AssumptionsCurrent-state map, Future-state map, Bottleneck list
Tagsno overlap
BacklogIterationDelivery
PrioritizationDeliveryEconomicsDecision
LeanEconomicsSequencePrioritization
LeanFlowWasteDelivery
Add more methods