Piloting SOA


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Piloting SOA

  1. 1. SOA Pilots Friday, February 16, 2007 Toll-free phone number (US/Canada): 866-469-3239 Call in phone number (US/Canada): 650-429-3300 Meeting number: 711 274 570
  2. 2. MomentumSI “At A Glance” Our Mission: MomentumSI provides expertise in the understanding, adoption and successful application of enterprise services and business process technologies. Headquarters: Austin, TX Offices: San Francisco, Washington D.C. and New York Founded: 1997 Business: Enterprise IT Consulting Focus: Enterprise Architecture & Integration Solutions Key Industries: Manufacturing, Banking, Insurance, High Tech, Pharmaceutical, Government Standards: OASIS, WS-I, OMG, J2EE, .NET
  3. 3. Speakers Alex Rosen VP, Enterprise Architecture Solutions In his more than a decade of IT consulting, Alex has provided architectural strategy and led implementation teams on projects for CNN, Time Warner, Bank One, Sprint, and others. Prior to focusing on EA, Alex developed significant subject matter expertise in content management and online commerce. Todd Biske Principal Architect, Enterprise Architecture Solutions Todd has over 5 years of SOA experience within Financial Services, including overall program management, Competency Center development, and infrastructure buildout. Prior to SOA, Todd focused on J2EE solutions, usability, and human computer interaction. He is a frequent blogger and speaker on SOA, and has a Masters Degree from the University of Illinois.
  4. 4. Agenda • Why do a pilot • When to do a pilot • What things to cover • Who is involved • How to run it
  5. 5. Why do a pilot
  6. 6. Why do a pilot • Need a showcase to justify continued investments • Validate what you think you know • Learn what you don’t know • Manage expectations • Operate with better than normal controls • Determine what it will take to establish a continued pattern of success
  7. 7. A Pilot is not a POC Proof-of-concept is a research activity. • Explore alternatives • Understand pros and cons • Relatively unconstrained • Can be a synthetic problem • Not intended for production - “throw away” Pilot is a production activity • Has business value • Can be used as a showcase • Fine tune policies and procedures • Intended for production
  8. 8. When to execute a pilot
  9. 9. MomentumSI SOA Maturity Model Levels of SOA adoption 0. Ad Hoc • No stated goal of SOA Adoption • No specific technologies associated with SOA • No specific roles associated with SOA • No specific processes associated with SOA • No specific training associated with SOA • ABOWS: A Bunch Of Web Services
  10. 10. MomentumSI SOA Maturity Model Levels of SOA adoption 0. Ad Hoc 1. Plan: Common Goals • Enterprise commitment to SOA adoption. • Stated role, purpose and direction for SOA. • Stakeholders and leaders are identified. • Understanding of SOA technologies and infrastructure. • High level plan, short-term roadmap and pilot projects identified. Must answer the question: Why SOA?
  11. 11. Establishing your goals • What are your primary reasons for adopting SOA? – Reduce costs – Faster delivery • What are the short-term drivers? – Connecting core applications – Partner integration – Master data management – Better visibility – Regulatory compliance – Multi-channel integration • What are the long-term drivers? – Faster product introductions – Flexible outsourcing – Business process improvement – Mergers and acquisitions
  12. 12. SOA Goals Drive SOA Pilots By documenting precise goals for SOA adoption, teams involved can more effectively choose the right projects, manage those projects, ensure that overall results are not derailed, and manage the expectations of the stakeholders.
  13. 13. MomentumSI SOA Maturity Model Levels of SOA adoption 0. Ad Hoc 1. Plan: Common Goals 2. Pilot: Build the Foundation
  14. 14. What should the pilot cover?
  15. 15. SOA Areas of Concern There are multiple areas associated with SOA adoption: • Technology Infrastructure • Organization • Approach and Governance • Enterprise Architecture • Communication and Training • Operational Management
  16. 16. Technology Infrastructure • Are new technologies or technology platforms being leveraged for the first time? • The pilot must address the processes associated with new technology. • Try to leverage staff from the appropriate teams where possible, rather than experts. • Don’t pilot too many new technologies at once.
  17. 17. Organization • Are you using the pilot to determine what roles are needed, or to pilot the interaction of people playing the new roles? • Centralized groups (shared services team, COE) must have a clear engagement model.
  18. 18. Approach and Governance • The hardest part in adopting SOA is the cultural change in moving to a service development organization. • A pilot that tries to tackle the culture change should involve at least 2 separately managed efforts- one for the service consumer and one for the service provider. • How will parallel development occur? • How will changes be managed?
  19. 19. Enterprise Architecture • SOA requires oversight beyond the boundaries of the project. • To a developer, EA and oversight is often a four-letter word. • Two responsibilities of EA need to be piloted – Reference Architecture: does it provide value to the solution/project architect? – Reviews: Did the review create unnecessary work? Were expectations clear?
  20. 20. Communications and Training • How are you going to spread the message of SOA to the organization? • How will you educate the staff? • Training pilots – Must have clear goals on expected level of knowledge post-training. – Attendees should be characteristic of those that need to be trained, not experts. • Communication pilots – Do you want the CIO or CEO to be the first person to receive the SOA message? – Make sure you have a way to measure the success of the communications.
  21. 21. Operational Management • Frequently tied to the adoption of new technologies. • Operations is often forgotten, but they are the most important. • Difficult to pilot- how do you pilot an unexpected production issue? • Pilot a change in the operational management behavior- proactive versus reactive.
  22. 22. Pilot Selection Process SOA Goals Pilot Goals • Reduce Costs • Key Service Creation • Faster Delivery • Reuse • Connecting Core Applications • Internal Integration Processes • Partner Integration • External Integration Processes • Master Data Management • Data Consolidation • Better Visibility • Service Metrics • Regulatory Compliance • Auditing Identify the goals of the pilots from SOA goals
  23. 23. The SOA Pilot Worksheet Key Service Creation Service Integration Metric Collection Goals Reuse Data Consolidation Service Auditing Approach and Governance Policies EA Involvement Service Lifecycle Mgmt Governance Parallel Development Consumer Onboarding SDLC Processes Service Ownership Project Mgmt. Organization SOA CoE Shared Services Team Process Analyst Schema Modeler Service Manager Service Librarian Operations Capacity Planning Configuration Mgmt. Reporting EA Ref. Application Arch. Process Driven Client Service Pattern Ref. Security Arch. Event Driven Discovery Pattern Process Analysis Service Identification Technology Web Services Invocation Libraries XML Registry/Repository Endpoint Container Data Integration Infrastructure Process Server Mgmt. & Monitoring Testing Tools Service Security Run Time Mediation Composition Tool Reliable Messaging Legacy Service Enablement Communication Training Curriculum and Training Broad Presentations Identify the goals Identify projects of the pilots from that may meet SOA goals pilot goals.
  24. 24. Selecting the Right Project • Project definition/selection can make or break the effort before it ever begins • Manage stakeholder expectations • Utilize the pilot worksheet to assess existing projects for suitability • More visibility = more risk = more reward Identify the goals Identify projects Achieve buy-in Revisit Project Revise as of the pilots from that may meet from project Specific Goals needed. SOA goals pilot goals. stakeholders.
  25. 25. Who should be involved?
  26. 26. Picking Teams • Choose people that will give the effort its best chance at success, however… • Don’t overload the pilot with experts, the pilot must extend to the rest of the organization • Staff must be representative of the real organization • Pilot team must be committed to the effort • Stakeholders must be committed to the effort, and willing to accept the bumps in the roads that will occur • Look for stakeholders that will be evangelists when the effort has completed • Share failure, success, and lessons learned • Communication will not happen automatically • Accelerate learning with use of outside experts
  27. 27. How should it be run?
  28. 28. Keys to Success • Conduct Technology POCs in advance • Manage expectations. – Revisit the project specific goals – Objectives must be clear to both the project team and the stakeholders. – Achieve buy-in from the project sponsors • Schedule needs to be flexible • Projects with high risk may not be the best choice, despite the value potential • Document decisions. • Remove barriers. • Position for success from the beginning. When the pilot efforts are over, you will be extending to the rest of the enterprise. Keep this in mind as you define and run your pilot projects.
  29. 29. Next Steps Levels of SOA adoption 0. Ad Hoc 1. Plan: Common Goals 2. Pilot: Build the Foundation 3. Extend: Methodology and Governance • Formal Governance Processes • Documented Methodology and Guidelines • Formal Communications and Training Effort • COE Shifts from doing to mentoring
  30. 30. Summary • Pilots can establish a pattern for repeated success • Establish your SOA goals first • Select one or more projects that provide adequate coverage across all areas of concern • Utilize a cross-functional team, committed to the effort • Manage expectations of all involved • Position the pilot for success from the beginning
  31. 31. Contact Us • Alex Rosen VP, Enterprise Architecture Solutions (919) 321-1034 arosen@momentumsi.com • Todd Biske Enterprise Architecture Solutions (618) 476-5119 tbiske@momentumsi.com