At the recent SOA in Action conference, I had the opportunity to join Miko Matsumura, vice president and deputy chief technology officer for Software AG, and John Favazza, vice president of research and development for WebLayers, Inc., in an in-depth roundtable discussion about the requirements behind SOA governance, and how this should be led. (Listen to the audio Webcast here, or read the full transcript here.)
Miko Matsumura, for one, said he is "seeing some amazing alliances" between the PMO and enterprise architects in the sense that "PMO is sort of the approval choke point of all projects. That is actually now starting to potentially open up to EA with respect to this notion to getting architectural review."
This adds even more teeth to SOA governance as well, he added. "You have to answer to EA and PMO together."
Another party that is increasingly weighing in on SOA governance decisions is the procurement department, Miko continued. "Procurement is stepping up and saying, 'you're going to buy what to do what?'" The procurement department also has teeth in the equation, since "ultimately at the end of the day the enterprise is going to have to pay the bill, especially when it comes to non-interoperable solutions that come from really scattered dispersed vendors."
John Favazza also is seeing more project management methodologies enter the SOA governance equation as well. "I do see that as eventually a lot of these project management tools and capabilities will merge with a lot of these governance technologies."
(Listen to the audio Webcast here, or read the full transcript here.)
Leave a comment