A recent article talks about ten mistakes that are made with SOA projects:
- Failure to explain SOA's business value.
- Underestimating the impact of organizational change.
- Lack of strong Executive sponsorship.
- Attempting to do SOA on the cheap.
- No SOA skills on staff.
- Poor project management.
- Viewing SOA as a project instead of an architecture.
- Underestimating the complexity of SOA.
- Failure to implement and adhere to SOA Governance.
- Letting the vendor drive the Architecture.
These issues are true for SOA, but they are also true for any IT project. SOA is new to most IT organizations. In the same way, new business software is new to a small business. Change the acronym to anything else, and you will have the same issues. In the past 30 years, significant effort has been expended by IT organizations to solve the overall problems. The failure rate is still very high. Even worse than absolute failure is that those organizations that feel that they have succeeded, do not get as much value from the implementation as they could.
As the article explains, the biggest issues relate to people and process. This is true of all technical projects. If these issues are not addressed, your chance of failure is high.
The full article can be found at: http://www.cio.com.au/article/253821/10_mistakes_cause_soa_fail?pp=6
No comments:
Post a Comment