We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.
Start a Discussion

In One Sentence, How Would You Make the Business Case for SOA Right Now?

Vote 0 Votes
In one sentance, how would you make the business case for SOA right now?

19 Replies

| Add a Reply
  • The business case depends on the scope of the development. At the Enterprise level you should make the business case for an EA effort that delivers SOA in a few iterations. The benefits enabled by SOA, that the business case has to financially quantify, are ultimately agility and potential outsourcing of processes and technology to best of breed suppliers.

    The SOA business case for software applications and suites is rather straightforward.

  • What is the business case for NOT using SOA? The only excuses are maybe (1) there is a package solution (think ERP) that does the job (or so you think), or (2) you need to move to a more EDA (Event Driven Architecture) - which most people agree is a subset of SOA anyway.

  • SOA is the paradigm shift for IT from a sense of entitlement to one of servitude!

  • Do it or risk becoming irrelevant - it's no longer a competitive advantage; it's the cost of doing business.

  • You don't make a business case for SOA. You use it to solve a business problem in a cost effective manner.

    • A snippet of clarification from an offline email conversation: It is a covert business case. I don't tell the the business I'm using SOA any more than I state I'm using Linux, .NET, MQ, the factory pattern, three tier architecture or any other technical approach. I just tell them it costs $X and will meet the requirements.

  • SOA creates repeatable capabilities to improve cross-functional processes, speedup IT project delivery and reduce IT redundancies.

  • You're already soaking in it!

  • Hi JP, is "servitude" a right word? Webster interprets it as a slavery. Is this what you meant?

  • Easy to change and adapt Responsive Organization.

  • While Paul Vincent is spot on in stating "when is there NOT a business case for SOA"; I also agree with Ed Nadrotowicz that you shouldn't be selling "SOA" to the business -- you sell a solution to their pain, and SOA is the foundation for that solution.

    • If you want broad support for a multi-year IT people and technology transformation, you need a clear and strong rationale. You will need this rationale or 'business case' even if SOA investment decisions are made entirely within IT.

  • It's not just about scalability - all other ity'ies are part of it.

  • Agree that it's hard not to make a business case for SOA, but you don't make the business case for SOA itself, rather the benefits of a solution underpinned with SOA. Increasingly in many spheres of software development, SOA (or subsets) is implied in the architecture already. This is exactly where we needed the evolution of SOA to go.

  • user-pic

    A couple of years ago already I put a lot of thought into this and came up with a paper called "your SOA needs a business case". Coincidentally I am currently applying this theory in a real client engagement. Aside from the numbers of the business case it has already proven to have huge benefits in setting the tone of the discussions. The idea has been embraced, now we're going to use it in a real situation, to come up with numbers. Is all about setting values to KAI's (Key Agility Indicators) Please read the full article and let me know what you think:

  • user-pic

    Almost forgot to summarize in a single sentence, here it is:

    Put a value to the increase in business agility!

Add a Reply

Recently Commented On

Monthly Archives