Service-oriented architecture is a way of including roles (customers, suppliers, engineers, etc.) and viewing everything as a service. Generally, we recognize services that are provided by people, machines and both. SOA is the most important development in the last ten years and is 1) Business-oriented - "describe what, not how" and 2) Message-oriented - "just ask and the service is given."
The concept of a service provided by people and machines forces both business and IT into alignment and to embrace the concept of a service. An excellent Business process management (BPM) practice is absolutely necessary to implement successful SOA projects.
Recently, I was fortunate to review many case studies focused on best practices in BPM. They are submitted yearly for judging from all around the world. The submissions represent public and private enterprises including finance, manufacturing, healthcare, water management, etc. The message contained in these studies, in my view, demonstrates that these practitioners are reaching a repeatable maturity level and the knowledge shared proved invaluable to me as a practice leader in the area who stands up around six clients a year in the BPM/SOA and TOGAF arena. I am dedicating this discussion to the benefits, best practices and pitfalls revealed in the studies.
What are the BPM/SOA benefits, best practices and pitfalls revealed by the people who have done it? I needed to boil down hundreds of observations and here they are:
- Increased business flexibility
- Very dramatic cost savings by creating business rules services
- Improved competitive advantage
- Increased revenues
- Improved worker productivity
- Improved customer service
- Reduced training costs
- Processing time reductions
- Process modeling for SOA-created visibility and accountability
- Establish a BPM/SOA/EA Center of Excellence (CoE)
- Ensure governance in SOA across all projects
- Think big - robust, scalable, secured, standards-based
- Start small - scale up while accumulating expertise
- Move fast - train staff, design and build in iterations
- Build out enterprise SOA services aligned with stakeholders strategic plan
- Focus on roles that require services that are delivered by a business process
- Develop and adhere to reference architectures, frameworks and open standards up front
- Focus on key dysfunctional process areas
- Knowledge of legacy environment
- Performance test your services and workflows
- Don’t "pave the cow paths" and create silo SOA
- Don’t underestimate SOA service work and modeling
- Don't forget to train managers in Agile management
- Don't lead with technology, ensure business and IT partnership
- Don't turn off legacy systems without learning contained business logic
- Don’t underestimate challenge of culture change
I observed that these clients are moving from a waterfall method to more agile approaches. Investments in modernizing BPM, SOA and enterprise architecture (EA) are allowing the early majority market to reap rewards. If your organization doesn't have a pilot BPM/SOA/EA initiative then your corporation may be at risk, much like corporations that did not catch the Internet wave and quietly disappeared.
What are your thoughts? Let us know.