<<Miko Matsumura, vice president of SOA product marketing for webMethods, says the path from an isolated SOA project to an initiative that spans various departments or business units crosses a Rubicon: "A new set of individuals entering into a federation is an inflection point. Each of these tribes brings their own culture. When you're running a pilot there's one tribe. Moving beyond the pilot means involving more cultures and that changes everything."
Simply put, good governance requires intense collaboration. The technical parts of SOA aren't the most difficult. Instead, the hard stuff centers on what some pundits call "Layers 8 and 9" of the OSI seven-layer model: economics and politics. Governance is all about managing Layers 8 and 9. (See also "Game plan for Team SOA.") In the book IT Governance, Peter Weill and Jeanne Ross define governance as "specifying the decision rights and accountability framework to encourage desirable behavior in the use of IT." According to Anil John, enterprise architect at Johns Hopkins University's Applied Physics Laboratory, "SOA governance should be considered an extension of existing IT governance that deals with the decision rights, processes, and policies that are put into place to encourage the adoption and operation of a SOA that may cross ownership boundaries." Governance deals with patterns of interaction, acceptable standards, and the creation of communication channels. Done right, governance also aligns the incentives in the organization with the goals of SOA and sets up SOA support structures. Scaling up IT governance to match SOA ambitions doesn't have to be paralyzing, boring, or difficult. All you need is a rational, collaborative approach.>> You can read the complete article at: <http://www.infoworld.com/article/07/03/05/10FEcollabgov_1.html?source=NLC-SOA&cgd=2007-03-08> Gervas
