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 PDCA Cycle.
Operations
PDCA Cycle
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Process Mapping method illustration showing its working structure
Operations
Process 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 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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-60 min1 h bis mehrere Wochen30-120 min1-3 h
Participantsdifferent
2-61-82-63-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationalePDCA Log, Experiment Plan, Learning Outcome, Standard ChangeObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
BacklogIterationDelivery
Continuous improvementLeanExperiments
LeanObservationProcessOperations
ProcessOperationsImprovement
Add more methods