For every service-oriented architecture (SOA) success story, there lays an abandoned SOA project stuck in one of the various stages of deployment.

Underscoring the successes and challenges of an SOA project is the popularized theory that 50 percent of IT projects are deemed unsuccessful. This, of course, can make embarking on an SOA strategy rather intimidating.

Still, SOAs remain at the top of the executive and IT agenda based on their ability to more closely align technology with the needs of the business. Quickly dismantling the high statistics associated with IT project failures, SOAs have shown demonstrable ROI.

In fact, the proven successes of SOAs have enabled this segment to swell to a worldwide market opportunity of $60.3 billion. This growth is up by 75 percent compared to 2005 when the market was estimated at $34.6 billion.

Moreover, the SOA market is expected to skyrocket with an anticipated 54 percent continued growth through 2008 to reach $143 billion, according to IT industry analyst Gartner. Furthering the growth of the SOA market is the strategy's ability to pay for itself quickly.

In fact, the number of opportunities for quick return on investment can be surprising. For example, many organizations are unaware of the number of duplicate processes that occur in separate departments and applications and how much these duplicate processes are costing them.

When you examine the costs and lost revenue attributable to redundant function and duplicated effort, you begin to see the value of centralized services over having to manage multiple competing and overlapping functions.

Still, there are some watchers out there asking: "How can SOA succeed where previous approaches have failed? How do I avoid becoming a statistic?"

These are powerful questions. Simply stated, a successful SOA strategy can be achieved because the standards, best practices and governance models have finally matured to the point where reuse can actually work.
After all, SOA is by definition an architecture as well as an approach to IT that can help solve immediate business challenges.

Though each company has different business needs and each industry faces its own set of challenges, there are common issues that can lead to the failure of an SOA. The 10 most prevalent are:

• Secure executive sponsorship: Before presenting how you'll ensure your company's SOA success, be prepared to demonstrate successes and failures of other companies on their path to SOA and articulate how you'll emulate proven practices and avoid pitfalls.
• Align the troops: Converse to overcoming the obstacle of executive support for your SOA is the challenge of aligning your organization to work and think in new ways. To do this, identify and recruit critical champions for each part of the business who will support and even evangelize the SOA efforts.
• Consolidate views: Eliminate the multiple views of information that are currently floating across your organization so you are only looking at a singular, comprehensive and consistent view of the business.
• Reuse: Identify and maintain a repository of your current Web services to avoid duplication of efforts. You may be surprised how much work has already been done by different pockets of your organization.
• Integrate the silos: Though in theory many of today's IT organizations seek to integrate and avoid redundancies while maximizing their current IT investments, the reality is that extraordinary efforts are being spent on still trying to maintain different IT systems that co-exist but are not integrated. The penny-wise, pound-foolish approach to SOA simply does not work.
• Seeing the forest through the trees: Remember that SOA is an architecture. It's not a combination of clumsily bundled together point products that need to be force fit. A true SOA is created with an open standards-based approach through four strategic stages: model, assemble, deploy and manage.
• Hop on the enterprise service bus (ESB): An ESB provides the much-needed connectivity infrastructure you can use to integrate services within an SOA. Together, an SOA and ESB help to reduce the number of complexity of interfaces. This can enable you to focus on your core business issues rather than on maintaining your IT infrastructure.
• Step by step: When the thought of rolling out an enterprise-wide SOA becomes overwhelming, remember that the best approach is to continually test and modify to identify issues while adding to your arsenal of best practices along the way.
• Avoid the 'carpe diem' approach: Remember that you're not building your SOA just for today or this year. This is an organization-wide approach to aligning IT with the needs of the business. It must accommodate today's needs as well as those of the future. For example, be sure to include support for mobile and wireless devices as well as ensuring you have enough flexibility to support the "next big thing".
• Prevent the accidental SOA: Many organizations may discover they have a healthy repository of Web services that will comprise the majority of their SOA. Still, they don't believe the SOA starts and ends with a collection of Web services. Remember that an SOA must go beyond Web services to support all your business processes. It must also provide a flexible, extensible and composable approach to reusing and extending existing applications and services as well as constructing new ones.