Development and Operations should have: * shared goals * common backlog of work * stored in a common work system * shared work queue * shared vocabulary * unified backlog * priorities of improvements from a global perspective by selecting work that has the highest value for the organization or mostly reduces technical debt
Any team member should be allowed to quickly help other team member or people outside the team.
Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations. The larger an organization is, the less flexibility it has and the more pronounced the phenomenon.
Organization of software and software team will be congruent: if you have four groups working on a compiler, you will get a four pass compiler.
Team organization has a strong effect on the produced software and architectural outcomes.
Overly functional orientation can cause undesired outcomes in the technology value stream.