Organizational Skills to Implement SOA
Before a company gets too far into designing solutions, it should access the existing skill sets of their people and the impacts of SOA on the culture and delivery capabilities.
If distributed computing, abstraction, loose coupling and service-orientation are foreign concepts to an organization, there obviously will be challenges to implementing SOA. These companies should seek help from consulting firms who have a proven track record delivering SOA, but they 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 you need to purchase software such as an ESB, BPMS or service management tools, you need to hire people to administer this software. Testersand infrastructure people 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 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 a well-established architect team already in place? If so, is it respected as a group that delivers value or is it 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, extendable, and truly reusable requires a consistent and well governed design process.
