The "Why" section introduces "Scale Free Architecture" and it is repeated several times, but not defined. When researching "Scale Free Architecture" we find examples in mathematics, computer networking, biology, etc., but it is not immediately clear how this pertains or not to a business structure of people and services. The answer is likely that scrum teams have a varying number of connections to other scrum teams, each connection having a guaranteed known stable interface of inputs (backlog) and outputs (potentially shippable increments) with transparency through standard work (events). However, this definition or a better one is not given anywhere online as of now, and not within the guide.
The "Why" section introduces "Scale Free Architecture" and it is repeated several times, but not defined. When researching "Scale Free Architecture" we find examples in mathematics, computer networking, biology, etc., but it is not immediately clear how this pertains or not to a business structure of people and services. The answer is likely that scrum teams have a varying number of connections to other scrum teams, each connection having a guaranteed known stable interface of inputs (backlog) and outputs (potentially shippable increments) with transparency through standard work (events). However, this definition or a better one is not given anywhere online as of now, and not within the guide.