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 Bottleneck Analysis.
Operations
Bottleneck Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Paper illustration for Theory of Constraints.
Operations
Theory of Constraints
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 flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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.For a system that does not get faster despite effort, the method directs attention to the bottleneck. It concentrates improvement on the point that actually limits throughput.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
30-60 min1-3 h30-120 min2-4 h Analyse, laufend
Participantsdifferent
2-63-82-63-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleBottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresObservation Notes, Improvement IdeasConstraint Map, Improvement Plan, Flow Metrics
Tagsno overlap
BacklogIterationDelivery
FlowMeasurementConstraints
LeanObservationProcessOperations
OperationsConstraintsFlowImprovement
Add more methods