On my todo list of topics to tackle in this blog is a discussion of new or evolved roles caused by adoption of SOA. A few entries ago I mentioned that "service choreographer" was my favorite potential job title, although I still haven't worked out the responsibilities.
Yesterday's email brought a piece by ZapThink called "SOA Governance: Reengineering IT Governance." In that piece, Jason Bloomberg starts to detail how SOA will affect traditional IT governance and some of the new roles it will create. I encourage you to take a look at it and see if it matches up with how you think your organization will go or at least needs to go. Bear in mind that multiple roles may be handled by the same person, and old roles will get modified and retitled in the process of adoption of SOA.
CBDI also looked at SOA governance in June in the larger context of Service Oriented Design. You will have to pay for this report, vs. the free ZapThink "ZapFlash" mentioned above. In my opinion, ZapThink and CBDI are among the leaders in the analyst community at comprehensively focusing on SOA and web services from both the business and IT angles. We're still early in this, so everyone's ideas will change and reflect the experience gained from the increasing number of concrete implementations, but these guys seem to really get it.