Sam Lowe, Capgemini, sam.lowe@capgemini.com

- The SOA has to pay off, otherwise it will loose credibility
- Why SOA bets?
 - Definitions of SOA differ and stakeholders are unclear
 - The roadmaps out there are unclear
 - An SOA initiative has to be a change programme

- Dont try SOA without knowing what it takes to be successful
- Where are the work-streams required and stakeholders involved?
- When should organizations use SOA explicitly, when implicitly and not at all?
- Check http://soafacts.com
- SOA is difficult and the implications are not well understood
- SOA Adoption:
 - New technologies
 - New industry standards
 - New skills and governance models
 - Stakeholder alignment
 - And indirect benefits case
 - Cross-organization impact
- The challenge: crossing the chasm (without disapearing down it)
 - How to prove the value and cross the chasm
 - How many architects really understand it?
 - What is necessary to succeed?
- Working out what you are trying to achieve
- Technology strategy combining existing with new
- Justifying to the leadership (and maybe to the board)
- Engaging the business
- Articulating to colleagues how it will affect them
- Develop the organization skills
- The definition of SOA seems to vary depending of the audience
 - Software View (ESB, WSDL, REST, SO, etc.)
 - Solutions View (Service granularity, Transaction Control, CBD, Composite Applications, BPM, Delivering Reuse)
 - Enterprise View: SOA enefits, Architecture capability, Service lifecycle Management, Service Modeling
 - Business View: Service Offerings, Outsourcing, Shared Services, Delivery Models, Asset reuse, Service Innovation
- We need to wok out how to communicate with the different groups
- Now everyone talks abou architecture, but it means something slighly different to everyone
- Everyone has a view of what it wants from architecture:
 - IT Leadership
 - Lines of Business
 - IT Delivery programmes
 - IT Operations/Support
- Where are the workstreams in SOA initiative?
 - Technology and Platforms
 - Applications and Services
 - SOA Methods and Capabilities
 - SOA Governance and Mandate
- Current State -> Future State:
 - SOA Tech strategy: "Have we got to the right technology?"
 - Applications strategy: "We are going to wait and see on Fusion/R4"
 - SOA Readiness accessment: "What are we missing?"
 - SOA Pilot design: "We dont know which project to use"
 - SOA Education Services: "They dont seem to understand that this affects them"
 - SOA Methods and Tools: "Its now growing beyond what we can directly control"
 - SOA Value Case: "I cant get X to agree"
 - SOA IT Operating Model: "We've shown it works but those B's in Project X wont play ball"
- Why should your organization be looking at SOA
 - Driven by business issues rather then technology
 - Including the necessary stakeholders across the organization
 - Pragmatic and focused on achievable benefits, mostly phased and incremental
 - Structured to generate business momentum
- What are the value propositions?
 - Reduce cost of new solutions
 - Improve asset reutilization
 - Reduce solution lead-time
 - The combination of these could be called: "increasing business agility"?
- Its essential to increase our ability to collaborate with the business
- Where should you use SOA: is there only one way?
 - Native SOA
 - Service Wrapped
 - Non-Invasive Architecture
 - No Architecture
- Where do SOA?
 - Areas of high business diferentiation are naturally aligned to SOA solutions
 - Large, high cost systemas are naturally aligned to architectural approaches
 - The more frequently organizations systems need to change the more deeply they should be aligned with a services model
- Jeff Scott's Mapping Technique: Understanding your stakeholders
 - Sponsor
 - Advocate
 - Supporter
 - Uncommited
 - Opponent
 - Adversary
- Who can be influentiated and who cant
- What the value system of those who cant is
- Sustainable SOA: understand their concerns and values and how it would affect them
 - IT Leadership (all of the others)
 - Business relatioship managers
 - Support and operations managers
 - Project Delivery Managers
- Pick the battles carefully for quick wins and early success
- Manage the roadmap like it were a programme plan
 - Engage potential pilot projects, Engage potential SOA project
 - Organization, Architecture, Delivery, Information and Services Modeling
- SOA is the first initiative that has architecture in its name. It has that pressure from the industry. We must see architecture as an whole when speaking about SOA.

Questions:
- Q: In a governance model who owns the service when it crosses several areas, like accounting, finantial, etc?
- A: Most people are not ready for concept of a service, they think about a system as a whole. Its a good question. A guideline would be people who understand the value of a service should own it.