Product Definition in Large Scale Scrum

This is the first part of a blog series about product definition in Large Scale Scrum.
In large product development, teams tend to work on just a part of the real product. The part—a narrow product definition– is often a component or a specific activity in the development process; it is not a product.
A narrow product definition creates all kinds of problems for a product group. It locally optimizes the performance of the teams at the cost of the performance of the group. The causal loop diagram (CLD) below explains this dynamic. ( See this blog for a quick overview of CLD notation. )
Product Definition Dynamics in LeSS
Narrow product definitions make it more likely to have specialized teams that only work in their silo, which in turn decrease adaptability and speed of learning at the overall product level. Broader product definitions lead to teams that cover multiple components and activities that together address the needs of end-users.
Remove Local Optimization Of Narrow Product Definition
A commonly used definition of a product is “something that is made to be sold.” The product provides a way of making a profit.
A product has users who are people;
A product provides features to those users that address their needs and problems;
A product has a business model, revenue stream, independent profit