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 Scrum |  Delivery Value Stream Mapping |  Agile Story Splitting |  Operations Waste Analysis |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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 process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 30-60 min | 45-120 min |
Participantsdifferent | 3-10 (Scrum Team) | 4-10 | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Current-state map, Future-state map, Bottleneck list | Smaller Stories, Acceptance Criteria, Split Rationale | Waste Map, Prioritized Waste, Improvement Backlog |
Tagsno overlap | AgileIterationCadence | LeanFlowWasteDelivery | BacklogIterationDelivery | WasteLeanProcess improvement |