10 tips on how to prevent business value risk
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
The content has been bookmarked!
There was an error bookmarking this content! Please retry.
Posted by Stefan Tilkov on Jan 20, 2007
Research firm Saugatuck Technology has released a report entitled “SOA Reality Check” that describes how and to which degree SOA is adopted in the field, namely among the 40 companies whose senior IT executives and IT architects were interviewed for the study.
In a freely available three-page document summarizing the report (PDF), the following key findings are highlighted (slightly edited for brevity):
Most firms deploying SOA are focused either on early-stage planning, and/or trial deployment around legacy application integration.
Of the thirty-seven percent of executives interviewed who indicated they are currently in a limited or full production stage of SOA deployment, many are merely managing a collection of web services, and have yet to make a strong commitment to SOA as a management discipline (as opposed to an integration technology).
Implementers are taking a technology-led approach to SOA deployment, even though earlier research showed almost universal agreement that business needs to be in the lead
The key long-term driver of SOA adoption – cost reduction – outdistances all others by a two-to-one margin. Unlike such technology revolutions of the past as client/server and minicomputers, users are also citing “code reusability” and “business agility” as strong secondary drivers of SOA.
According to Saugatuck, the three key inhibitors need to be overcome for successful SOA adoption are upfront cost, resource sharing and allocation, and SOA governance. Another finding was that typically, SOA adoption occurs in three “waves”:

The full report, which documents the three adoption waves, the promise of SOA, adoption trends, business drivers, inhibitors, lessons learned, and recommendations, is available via Saugatuck’s web site for $1,295.00 USD.
One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.
InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.
Alex Papadimoulis discusses ugly code, where it comes from, how to avoid it, and how to get rid of it.
John Davies examines Visa’s architecture and shows how enterprises have architected complex integrations incorporating Hadoop, memcached, Ruby on Rails, and others to deliver innovative solutions.
Sean Comerford unveils ESPN.com’s architecture, what components are used and why, and the current changes the website goes through.
Are there repeated patterns of failure on Enterprise Agile Enablement efforts? Sanjiv and Arlen discuss Seven Deadly Sins to avoid when adopting Agile in an enterprise.
Erik Dörnenburg answers: What is Enterprise and Evolutionary Architecture?, discussing 4 issues: Turning strategy into execution, Ensuring conformance, Where do the architects sit? Buying or building?
Sean Cribbs explains what Map-Reduce and Riak are, why and how to use Map-Reduce with Riak, and how to convert SQL queries into their Map-Reduce equivalents.
No comments
Watch Thread Reply