Expert analysis, advice and prognostications about Service Oriented Architecture and distributed computing.
Our bloggers: Mike Kavis is a veteran Chief Architect with over 23 years of IT experience including distributed computing, SOA, BPM, data warehouse, business intelligence, and enterprise architecture. Former applications developers Rich Levin has been implementing, advising on, and writing about information technology for over 20 years, covered computer technology for CBS Radio and hosts the popular "PC Talk" show. Nicholas Petreley is a former programmer and consultant, has worked for InfoWorld, Computerworld, LinuxWorld and Network Computing World, webzines, and serves as contributing editor for CIO, focusing on SOA as a primary area of coverage.
Does Your Organization Have the Skills to Implement SOA?
Keywords: SOA, Organization, Consultants, Culture, Ivory Tower
Skill Set Assessment
If distributed computing, abstraction, loose coupling, and service-orientation are foreign concepts in an organization, it will be challenged to implement SOA. These companies should seek out help from consulting firms who have a proven track record delivering SOA, but should not let the consultants run the show. There should be a strong technical leader who understands SOA and can set the strategic vision. The consulting firms should complement this person and help the company realize the vision. The consultants' goals are to maximize revenue. The IT leader's goal is to deliver SOA without breaking the bank! If a company does not have a strong technical leader with great business and people skills, it should hire someone. This person will cost top dollar but the initiative will likely fail without the right person in charge.
SOA requires specialists in many areas. A company implementing SOA will likely need enterprise architects, data architects, security specialists, process modelers, integration specialists, process analysts on the business side, and various types of developers. If there is a need to purchase software such as an ESB, BPMS, service management tools, etc., there will be a need to hire people to administer the software. Testers and infrastructure people will need to understand the concepts of SOA. It would be wise to consider bringing in an expert or two in this area as well.
Budget for a large amount of training. Everybody is impacted by SOA. The DBAs, configuration management personnel, project managers, testers, developers, architects, the business, and all of the specialists I mentioned above will need various types of training. One of the greatest cures for resistance to change is knowledge. The more these people understand SOA and its potential benefits, the less they will resist it.
Culture Assessment
What is the current culture like? Is there already a well established architect team in place? If so, are they respected as a group that delivers value, or a group of ivory tower philosophers? Does the organization have established standards to which people adhere, or do the individual teams make their own rules? The answers to these questions have a huge impact on the effort required to deliver SOA. Cultures that value enterprise architecture, governance, and standards will have a much easier time adapting to SOA then companies that do not have controls in place. Building services that are abstract, loosely coupled, extensible, and truly reusable requires a consistent and well governed design process.



