Wednesday, July 23, 2008

Reasons Why People are Responsible for SOA Failure

Mike Kavis from Techworld posted this informative article on what makes SOA fail in businesses. In summary he provided these 10 reasons of why people are responsible for the failure:

  1. Fail to explain SOA’s businesses value
  2. They underestimate the impact of organizational change
  3. They fail to secure strong executive sponsorship
  4. They attempt to do SOA “on the cheap”
  5. They lack the required skills to deliver SOA
  6. They have poor project management
  7. They think of SOA as a project instead of architecture
  8. They underestimate the complexity of SOA
  9. They fail to implement and adhere to SOA governance
  10. They let vendors drive the architecture

It was interesting to see his opinion on what needs to change in the way in which people incorporate SOA into their respective organizations. What are your viewpoints on what makes SOA work in the workplace? Can you think of any improvements you would recommend for individuals within companies?

No comments: