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 for Kaizen Event.
Operations
Kaizen Event
Paper illustration for PDCA Cycle.
Operations
PDCA Cycle
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.For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments.For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.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
MediumMediumLowMedium
Timedifferent
30-60 min0.5-5 Tage1 h bis mehrere Wochen1-3 h
Participantsdifferent
2-64-101-84-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleKaizen Charter, Waste List, Improvement Experiments, Standard Work UpdatePDCA Log, Experiment Plan, Learning Outcome, Standard ChangeCurrent-state map, Future-state map, Bottleneck list
Tagsno overlap
BacklogIterationDelivery
LeanContinuous improvementOperations
Continuous improvementLeanExperiments
LeanFlowWasteDelivery
Add more methods