View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Story Splitting |  Delivery Value Stream Mapping |  Operations After-Action Review |  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. | 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. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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 | Medium | Medium | Low | High |
Timedifferent | 30-60 min | 1-3 h | 20-45 min | 2-4 h Analyse, laufend |
Participantsdifferent | 2-6 | 4-10 | 3-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Current-state map, Future-state map, Bottleneck list | Lessons learned, Action items, Event summary | Constraint Map, Improvement Plan, Flow Metrics |
Tagsno overlap | BacklogIterationDelivery | LeanFlowWasteDelivery | LearningOperationsImprovement | OperationsConstraintsFlowImprovement |