Project Selection
Most of us would agree that service-oriented architecture (SOA) doesn't happen overnight-you need long-term investments. But we also know that businesses need immediate returns on IT spend. With this dilemma, how does an IT manager build out SOA while returning value on incremental SOA investments? The answer lies in judicious project selection and will be the focus of this second article in the Path to Level 5 SOA series. The first article discussed how to assess your SOA readiness to get an understanding of the gaps between current capabilities, that is, your current maturity, and future goals. In project selection, you fill out the gaps and build out your SOA by identifying IT projects that provide business value.
Build Out Your SOA, a Project at a Time
Now that you understand what capabilities you need to enhance, how best to proceed? Executing on projects is the most pragmatic approach to fill capability gaps in your architecture and infrastructure. The SOA approach does not require you to spend months defining an architecture or making people changes in isolation. If you are starting out new, we believe, SOA is best absorbed in an organization by selecting a pilot project that has immediate business benefit. And if you demonstrate success early, you will have a string of SOA projects in the pipeline. With each project, you bring in additional product components, enrich your service portfolio, and enhance your architecture. With a rich service portfolio, identification of services required to compose an organization's business process is faster and reuse is maximized-eventually moving you up the maturity model. We also believe that SOA adoption is suited for an incremental approach, unlike the big bang approach for monolithic systems, with additional SOA components increasing the value of existing components exponentially. In this context, project selection becomes a critical activity.
