SOA Maturity Model

The phases of the maturity model include:

• Early Learning
• Re-engineering
• Integration

• Maturity

 Early Learning

In the early learning phase is where an organization begins the journey to adopt SOA. During this phase is where the Enterprise Architecture function is founded and staffed with the leaders of the SOA definition and adoption program. Also, small cores of service procurement and operations resources are assembled. In Early Learning is where the first revision of the service taxonomy, roadmap, and foundational architecture decisions are made. Success metrics are defined along with a working financial model to project the investments and associated financial returns expected from the SOA roadmap. Finally, in early learning an appropriate number of hands-on proof-of-concept and pilot projects should be completed to demonstrate the viability of the services, service infrastructure, and associated architecture. As part of these pilot projects, documentation regarding key learnings and shifts in operational policy should be delivered to the organization in preparation for the ramp into the Re-engineering phase.

 Re-engineering

Re-engineering is the phase where the SOA adoption roadmap gets out of the lab an into the software factory. At this point the Enterprise Architecture team will have completed the definition of the first generation services inventory, the architecture for the services infrastructure, and have defined an approved roadmap for solution adoption. The starting team of Service Procurement and Operations will have established a “pilot light” of services and infrastructure that provide real working examples for additional engineering and project manager resources to handle and understand the shift to SOA. During reengineering a shift of resources from the built-to-order or made-for-order teams will migrate to the Service Procurement, Operations and Service Assembly teams. At this point there should a number of production solution development projects underway which leverage the services inventory and infrastructure to deliver the application functionality. During re-engineering the beach-head of the assemble-to-order software factory is definitively established.

 Integration

Once re-engineering is completed, the integration phase will begin. Integration starts when a mature service inventory and infrastructure is established and the first phase of identified solutions on the Enterprise Architecture roadmap have transitioned to SOA. The Enterprise Architecture and Service Procurement teams are fully established and at a reasonably mature state of operation. At this point, multiple and simultaneous teams will address the remaining targeted business domains on the roadmap and initiate the transition to SOA. Integration will involve continuous improvement to the service inventory and infrastructure as well as a substantial rise in the Solution Assembly and Operations teams. At this point, the established metrics and associated communications processes should be driving adjustments to the future roadmap.

 Maturity

Once re-engineering and integration phases are completed, then you enter the maturity phase of the roadmap. Maturity is a state where that the material defined aspects of the service inventory, infrastructure and organizational shifts are completed and work going forward is primarily focused on continuous improvement from the foundation established by the Integration phase. At this point the full shift to an assemble-to-order manufacturing model is completed.

It is important to pace technology investments, organizational shifts and new funding/reward policies in alignment with one another. You do not want to be crawling in one area while running in another … doing so will cause you to trip in the execution of the SOA transition.