Barriers to SOA adoption

ZapThink is getting a lot of coverage from a recent post blaming the IT department as a barrier to SOA adoption. See also discussion by Todd Biske.

I went through the first couple dozen hits on Google for "barrier SOA adoption", and identified a number of competing ideas. (Some links no longer current / available.)

The Organization Itself

says CBDI

IT Department

says Zapthink

XML Skills

says Perficient

Lack of Business Justification

says IDG

Vision, People, Management and Resources

says InfoSys

Lack of awareness and familiarity with SOA

says Vinita Gupta, journalist

Complexity

says BEA

IT Integration and Flexibility

says Sandy Carter of IBM

Detangling the web of applications and old systems

says NSW Police

Lack of discretionary spending in IT

says Dana Gardner of Interarbor Solutions

The Desktop

says ZDNet

Resistance to Change

says IDC

---

Additional resources on SOA adoption

Roadmap - PGFSOA Wiki

A Roadmap for SOA adoption - from the Practical Guide to Federal SOA (PGFSOA)
See also PGFSOA Version 1.1 (PDF June 2008)

CBDi Web Services Roadmap

CBDI Web Services Roadmap - Guiding the Transition to Web Service and SOA

Richard Veryard on SOA Adoption

Selected posts from Richard Veryard's SOAPbox blog.

---

Todd Biske adds

While resistance to change and the organization itself are somewhat the same thing, my instinct is that it's the broader organization that is typically the barrier, and it's usually that the entire org is resistant to change. (May 11, 2007)

Updated 18 Feb 2016