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 Arnon Rotem-Gal-Oz on Aug 27, 2007
I say good. Good riddance to the droves of hypesters, amplifiers and marketing managers that couldn’t stop themselves from slapping a $OA label on anything or one that recognized http or used an angle bracket.Brenda then continued to list the things that should be addressed such as properly defining SOA, identifying real business problems SOA can help with, defining methods to deliver actual solutions, go beyond the vendor packaging of SOA components, figure an agile way to implement SOA and lastly:
As for the rest of us, those who “get” SOA and its true value proposition, it is time to reclaim SOA. To start, we need to remove the large obstacles on the SOA business value path.
Let’s consider, plan, measure and report on SOA in the correct perspective, as a lifestyle change that encompasses people, process and technologyAt the end of the day it seems that behind the hype cloud, real SOA experiences are starting to emerge. Development teams are realizing productivity gains, but whether or not they would also translate to business ROI depends on the actual business case that is behind the SOA initiative. Doing SOA just for the sake of SOA will not yield a lot of benefit.
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