| Title: |
The SOA Maturity Model |
| Author: |
David Sprott |
| Publication Date: |
20 December 2005 |
| Report Type: |
Journal |
| Report Class: |
Best Practice |
| Abstract: |
Adopting SOA is a medium to long term program for any enterprise. There are many different strategies that can be adopted and the right approach will be specific to every organization. However there is a high level of commonality in the generic capabilities that are applicable to every enterprise and a maturity model can provide guidance in both planning and monitoring progress. CBDI first published a Web Services and SOA Maturity Model in 2003. Since then we have learnt a lot and in this report we update our maturity model to consolidate the experience of working with numerous early adopting enterprises. We also take a look at other maturity models that have been published recently.
|
| Backgrounder: |
A maturity model is a guide for process improvement. The nature of any generalized maturity model is that there is no right or wrong approach, rather the model is a framework that provides a set of benchmarks which may be helpful to an organization in developing it’s own approach. The maturity model is a basis for planning and managing change. It suggests areas where capability can be measured in a systematic manner so that the appropriate level of trust can be vested in the organization at a given point in time, tempering the optimism of the over enthusiastic with practical assessments of actual capability.
A good way to think about this is that the maturity model focuses on the what not the how. It identifies what the capabilities are at various levels of relative maturity.
In updating the CBDI Web Services and SOA maturity model1 we have continued our original approach of taking a very broad perspective. We recommend that a good maturity model will be strongly process based, and have a scope that is much broader than simply technology usage capability. We believe this is important because SOA and CBD (component based development) are long term transformation programs which will eventually have a very profound impact on existing organizations. In offering a revised SOA maturity model we aim to provide a framework which encompasses many different stakeholders, and encourage others to further develop and specialize the model.
Over the past few years we have used the original CBDI model as the foundation for our numerous roadmap workshops. The concepts of phases and streams have been really useful planning devices. What happens in practice is that the maturity model provides the generalized framework that can guide the development of an organization specific roadmap.
In this report we commence by commenting on several recently published models that have some direct relevance to SOA and then develop our earlier models further. |
| Report Size: |
10 pages |
| Report Access Type: |
 | Silver/Gold (Premium) |
|
| Available for separate purchase |
Single copies of recent CBDI Journals may be purchased |
| Login |
|
Home