There is a tremendous amount of compliment in books, and in the blogosphere, for cross-functional teams. It sometimes seems as though it’s the best idea since cross-personal interaction. And cross-personal relationship is a great idea, until you find out you caught some public disease you’ll rather have prevented.
I am pleased that I have little experience with interpersonal diseases, but I do know that at least part of the compliment for cross-functional teams is undeserved. There are a variety of myths because some writers associate functional groups with hierarchies and cross-functional teams with organic networks. But this is both unfair and unrealistic.
Functional teams require coordination across team boundaries about the projects these are doing, and the business value sent to customers. On the other hand, cross-functional teams require coordination across team boundaries about practices, standardization, and shared resources, for just about any similar kind of work that is completed in different teams.
In the previous section, we saw which you have two options for coordination: DP1 and DP2. Both can be employed to either functional groups or cross-functional groups. Coordination between functional teams is conducted by managers (typical hierarchical functional silos). Coordination between functional groups by the groups themselves (for example, self-organized sysops teams each focused on a piece of an infrastructure).
Coordination between cross-functional teams by a project supervisor or other government bodies above the teams. Coordination between cross-functional groups by the groups themselves (for example, a “Scrum of Scrums”). Figure 13.7 Quadrant of organizational styles. In general, …