We purchased IBM's WebSphere Message Broker and established an SOA governance structure. We're in the process of building an "Integration Team" that will operate the ESB and develop message flows and services, and help the divisions build services too.
MIT Lost initial momentum.
LF note: considerable SOA architectural work at MIT in 2007. See http://web.mit.edu/itag/eag.html
If there has been a significant change, can you identify the top 3 drivers for that change?
We realize that we are still mostly at the "ad hoc" phase and there are frequent discussions with the divisional IT staff to educate them on the benefits of SOA.
The push for Project management has interfered with establishing and adhering to architectural goals