When it comes to SOA/Web services, striking the right balance between what business units need and what IT departments deliver is difficult.
According to an InformationWeek Research Web survey of 273 business-tech pros last month, 24% of respondents using SOA and Web services say the projects fell short of expectations. Of those, 55% say SOA projects introduced more complexity into their IT environments, and 41% say they cost more than expected. Out of all respondents using SOAs and Web services, just 7% say the results exceeded expectations.

"Where I've seen great technology projects fail is when business doesn't see it as important," says Terri Schoenrock, Hewlett-Packard's executive director of SOA. More than a quarter of SOA projects she's seen have fallen short of expectations. "And it's usually about business and IT alignment problems."
Read full article at InformationWeek
Source: 1
Prashanth Rai
Mr Wong
Vote for SOA is difficult:
|
Rating: 7.33 out of 3 vote(s) cast.
|
-
Online MBA Degrees - earn your mba degree online with one of hundreds of programs available at elearners.com
| RSS | See all blog subscribe options |
|
What is RSS? | |
| Yahoo! |
|
| Addthis |
|
| Bloglines |
|
| Newsletter | |
| Follow us on Twitter! |











The approach must be both bottom up and top down.
Bottom up: Because the technology to build a Web service is new. From designing industry compliant WSDL contracts, to developing the services, to learning how to test a Web service are all new. So even doing point-to-point services within one department is important. This way when departments begin to integrate and place their services into the SOA they have some expertise.
Top down: Since these new applications will involve services that go across LOB there are two important parts that need to come from the top. The first is control of granularity. Each business will have a service granularity that works best for their needs. Some companies may have just a few large services while others may have hundreds of smaller services. This will depend on business needs and should be controlled from the top. Also the SOA is going to need some infrastructure to support it. Most notably is a registry and quality. Quality needs for a SOA are different than for just and application. Quality leads to trust, trust leads to reuse, reuse leads to agility and the real ROI.
But as you have probably noticed all of this is cultural change on how your people are building applications. Change takes time.
Frank Grossman
CTO
Mindreef