piloting soa
DESCRIPTION
TRANSCRIPT
SOA PilotsFriday, 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
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
MomentumSI “At A Glance”
Speakers
Alex RosenVP, 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.
Agenda
• Why do a pilot
• When to do a pilot
• What things to cover
• Who is involved
• How to run it
Why do a pilot
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
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
When to execute a pilot
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
MomentumSI SOA Maturity Model
Levels of SOA adoption0. 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?
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
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.
MomentumSI SOA Maturity Model
Levels of SOA adoption
0. Ad Hoc
1. Plan: Common Goals
2. Pilot: Build the Foundation
What should the pilot cover?
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
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.
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.
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?
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?
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.
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.
Pilot Selection Process
SOA Goals
• Reduce Costs
• Faster Delivery
• Connecting Core Applications
• Partner Integration
• Master Data Management
• Better Visibility
• Regulatory Compliance
Pilot Goals
• Key Service Creation
• Reuse
• Internal Integration Processes
• External Integration Processes
• Data Consolidation
• Service Metrics
• Auditing
Identify the goals
of the pilots from
SOA goals
Technology
Infrastructure
The SOA Pilot Worksheet
Goals
Organization
Approach and
Governance
Operations
EA
Registry/Repository
Process Server
Service Security
Reliable Messaging
Governance Policies
Endpoint Container
Composition Tool Run Time Mediation
Invocation Libraries
Testing Tools Mgmt. & Monitoring
Legacy Service Enablement
Web Services
Discovery Pattern
Client Service Pattern
Ref. Security Arch.
Ref. Application Arch.
Process Analysis
Process Driven
Event Driven
EA Involvement
SOA CoE
Parallel Development SDLC Processes
Project Mgmt.
Service Manager
Process Analyst
Service Librarian
Capacity Planning
Data Integration
Configuration Mgmt.
Key Service Creation
Reuse
Service Integration
Data Consolidation
Metric Collection
Service Auditing
Service Lifecycle Mgmt
XML
Shared Services Team
Consumer Onboarding
Service Ownership
Schema Modeler
Communication
and Training Broad Presentations
Training Curriculum
Reporting
Service Identification
Identify the goals
of the pilots from
SOA goals
Identify projects
that may meet
pilot goals.
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
of the pilots from
SOA goals
Identify projects
that may meet
pilot goals.
Revisit Project
Specific Goals
Achieve buy-in
from project
stakeholders.
Revise as
needed.
Who should be involved?
Picking Teams
• Choose people that will give the effort its best chance at success, however…
• Don’t overload the pilot with experts, the pilotmust 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
How should it be run?
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.
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
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
Contact Us
• Alex Rosen
VP, Enterprise Architecture Solutions
(919) 321-1034
• Todd Biske
Enterprise Architecture Solutions
(618) 476-5119