Rationalizing SOA for success



Email    print   
February 3, 2009 —  (Page 1 of 6)
In these uncertain economic times, IT budgets are tightening and service oriented architecture projects are at risk of flat lining. One of the keys to sustaining long-term SOA buy-in is implementing projects incrementally, ensuring success while minimizing organizational change—and generating revenue to boot.

Knowing how to successfully implement SOA requires an understanding of why some projects have failed. SOA has significant organizational change implications, and overly ambitious projects can be unsustainable due to high upfront costs and low initial return on investment.

"SOA is not just a technology change, it is something that needs to be dealt with like any other business change," said WSO2 CTO Paul Fremantle.

SOA challenges organizations and organizational funding models, he explained. "People in the organization feel threatened by change, and companies have taken on SOA without realizing there would be resistance."

Many organizations like to keep their silos clean and push cost and complexity onto other groups, said Miko Matsumura, deputy CTO at Software AG. "For every silo, there is a tribe with its own political interest to horde things."

One of the principles of SOA is software reuse, and organizations benefit through increased agility and cost savings when there is more sharing of resources, Matsumura said.

"The question is translating what enterprises want into the behavior of an organization and individuals," he said. "Tribes act in their own self interests, and the value of SOA can quickly fall way by the wayside."

Matsumura suggested that organizations connect behavior to motivational drivers such as job reviews, bonuses and other compensation. "Organizations should structure incentives programs and link them to best practices behavior," he said. "Without discipline, air goes out of the tires. When the kids fight, you've got to call dad. Executives should be engaged at a reasonably high level."

Specifically, C-level executives are needed to sustain the effort, Matsumura said, explaining that it is because those executives witness the cost of the bickering.

"There is a natural alliance between architects and executives: The architect sees the big picture, and the C-level pays for the big picture," he said. He added that executives also need to have a clear understanding of the implications of SOA.



Related Search Term(s): finances, professional development, SOA

Pages 1 2 3 4 5 6 


Share this link: http://sdt.bz/33238
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
SOA Software releases project-planning suite for SOA transition
Portfolio Manager provides a framework for SOA planning, helping developers prioritize services, understand dependencies, and plan architecture and governance processes, the company says. The product is marketed as being essential for creating road maps for transitioning to SOA Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb