Kavis, Mike: 10 Mistakes that Cause SOA to Fail; in: CIO Magazine, 01. October 2008.
I usually don’t care much about these industry journals. But since they arrive for free in my mail every other week, I could help but noticing this article, which gave a brief overview of two SOA cases – United’s new ticketing system and Synovus financial banking system replacement.
However, the ten mistakes cited are all too familiar:
- Fail to explain SOA’s business value – put BPM first, then the IT implementation
- Underestimate the impact of organisational change – create change management plans, follow Kotter’s eight step process, answer everyone the question ‚What’s in it for me?‘
- Lack strong executive sponsorship
- Attempt to do SOA on the cheap – invest in middleware, invest in governance, tools, training, consultants, infrastructure, security
- Lack SOA skills in staff – train, plan the resources, secure up-front funding
- Manage the project poorly
- View SOA as a project instead of an architecture – create your matrices, war-room; engage collaboration
- Underestimate SOAs complexity
- Fail to implement and adhere to SOA governance
- Let the vendor drive the architecture