That's a good point, but how do you bring the two sides together in the first place?
Putting them in the same room to talk about something other than the latest requirements document is a good start. Bell Canada asks 1,700 business and IT staffers to attend annual "summer camps" of classes designed to bring each side up to speed on the other's most pressing challenges and foster a real conversation between the two.[*] The company has also begun to seed its higher-level IT positions with executives from business backgrounds in order to keep those conversations going internally on the IT side. Those are two small steps, but they should give you an idea of the organizational and cultural commitments necessary to open the lines of communication between the two. Asking them to collaborate on next-generation architecture will be a little more difficult, but it can be done.

Figure 3-6. Culture change: from org chart to processes and opportunities
ESA adopters might borrow a page from the manufacturers who pioneered the concept of "concurrent engineering," in which representatives from every relevant department within the organization imagine entire product life cycles from conception through design, manufacture, introduction, and even disposal. At every step, designers and engineers can argue for cost-saving modifications or alternate techniques to achieve the same goals. Through close collaboration, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access