Projects + Management = The Project-Management Blog

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:

1. Fail to explain SOA’s business value - put BPM first, then the IT implementation
2. 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?’
3. Lack strong executive sponsorship
4. Attempt to do SOA on the cheap - invest in middleware, invest in governance, tools, training, consultants, infrastructure, security
5. Lack SOA skills in staff - train, plan the resources, secure up-front funding
6. Manage the project poorly
7. View SOA as a project instead of an architecture - create your matrices, war-room; engage collaboration
8. Underestimate SOAs complexity
9. Fail to implement and adhere to SOA governance
10. Let the vendor drive the architecture

This entry was posted on Dienstag, Januar 6th, 2009 at 18:37 and is filed under IT Project, Failed Projects, Software Development. You can follow any responses to this entry through the RSS 2.0 feed. Responses are currently closed, but you can trackback from your own site.