View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Value Stream Mapping |  Delivery Cost of Delay |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-3 h | 90-180 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-10 | 3-8 | 3-20 Reviewer |
Formatdifferent | Workshop | Workshop | Async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | CoD Table, Prioritization Sequence | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | LeanFlowWasteDelivery | PrioritizationDeliveryEconomicsDecision | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
