Talk:Value stream

The Scaled Agile Framework is referenced as a methodology that uses value streams. However, SAFe actually redefines what a value stream is and it should not be referenced this way. It's redefinition of a value stream is harmful. I am not sure how to make these corrections. Is there an owner of this page? Updated by Alshalloway (talk) 13:44, 15 August 2020 (UTC)alshalloway

Adding a contradicting view to talk page. Removed this section: "Or rather, value streams are not represented as process flow diagrams. Clearly, a value stream is a process in the sense that it is an end-to-end collection of activities that lead to a result of value to the consumer of that result. However, value streams are representations that do not sequence all the activities under control logic."

The reference for this bullet (fixed the URL, btw) - clearly states that the concern of a value stream is "how value is achieved", while the concern of a process is "how it's done". As they are defined differently - and the concerns are different - in literature, it is incorrect to say that "a value stream is a process" because it shares some characteristics. Thanks!

"A value stream always begins and ends with a customer." It is more correct to replace "customer" with "user". The customer typically is the person who buys a product or service. In bigger companies this typically is not the person who is using the product. A value stream always starts and ends with a user. — Preceding unsigned comment added by 85.145.196.177 (talk) 10:04, 25 August 2022 (UTC)