The most popular and comprehensive Open Source ECM platform
SOA: 10 ways that SOA is Failing
Netherlands-based TechWorld blogger Mike Kavis echoed Burton Group’s assessment that SOA failures are most often a result of problems with people and business culture based rather than technology problems.
Kavis identified 10 reasons for SOA failures. His top five reasons include:
1. Lack of clarity around SOA business value
Failure to match SOA to business problems and processes is the biggest problem. It’s better to work backwards from business problem, drafting a solution, rather than first trying to invest in technology that will later be applied to general business problems.
2. Lack of understanding of the potential impact of organizational change.
Workflow, Re-engineering, and now SOA involve business process changes as part of the solution. Changes in the workplace inevitably become political as people try to determine what change means for their place in the organization. Kavis recommends creating an organizational change management plan to address potential problems.
3. Lack of an executive champion
Without involvement and sponsorship from someone high up in the organization, an SOA project is destined to fail. The project should be aligned with key business drivers and structured in a way to attract the full support of a CXO-type executive.
4. Lack of Budget
The technoloogy costs of SOA include costs for governance tools, training, consulting, infrastructure and security. Trying to skimp on the investment in these tools and consulting needed to bootstrap the effort can lead to disaster. The better approach is to determine potential ROI and use that as a justification for receiving adequate funding.
5. Lack of SOA skills
Skill sets focused on SOA include architects, business process modelers, administrators. SOA implementations can be complex and skills both on the technology and business sides are needed to be successful. The overall SOA plan should include money and time for training and resources.