The standard depiction of a software development value stream begins with coding and ends with code in production.

Taking a step back, you see many more activities involved in supplying software to customers, but current approaches to managing these activities are rooted in service delivery frameworks and not in production models.

The model used in other product industries is the supply chain model, and by applying that model to software delivery, you can expand your understanding of the software delivery “system” beyond devops, giving you new insight in to how to optimize it.

The extent of planning activities is often minimized by existing devops models.

Lack of communication and connections between development processes using agile and nonproduction activities using waterfall can lead to waste and inefficiency across the business.

In the traditional supply chain, sourcing components involves managing relationships with suppliers and developing procurement strategies for parts and materials.

The text above is a summary, you can read full article here.