The Organizational Soa Roadmap

2,491 views

Published on

How to setup organization for successful SOA

Published in: Business, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,491
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
83
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The Organizational Soa Roadmap

    1. 1. The Organizational SOA Roadmap Byungwook Cho K. 2006-06-14
    2. 2. Agenda <ul><li>Stakeholders and Potential Conflicts of Interest </li></ul><ul><li>The Organizational SOA Roadmap </li></ul><ul><li>Four Pillars for Success </li></ul><ul><ul><li>Budget </li></ul></ul><ul><ul><li>Project </li></ul></ul><ul><ul><li>Team </li></ul></ul><ul><ul><li>Buddies </li></ul></ul><ul><li>An Ideal World </li></ul><ul><ul><li>Structures and processes </li></ul></ul><ul><ul><li>SOA Specifies </li></ul></ul><ul><li>Examples in The Real World </li></ul><ul><li>Recommendations for the SOA Protagonist </li></ul>
    3. 3. 1. Stakeholder and Potential Conflicts of Interest <ul><li>Before introducing SOA, we need to examine who the different stakeholders in the SOA are within an enterprise and the potential conflicts of interest that you must overcome to ensue a successful introduction of new technical standard. </li></ul>
    4. 4. 1. Stakeholder and Potential Conflicts of Interest <ul><li>Obstacles to SOA investment </li></ul><ul><ul><li>Intangible ROI </li></ul></ul><ul><ul><li>Frequent changes in strategy </li></ul></ul><ul><ul><li>Gap between IT and Business </li></ul></ul><ul><ul><li>Not Invented here syndrome </li></ul></ul><ul><li>ROI is not tangible </li></ul><ul><ul><li>No way to measure SOA value </li></ul></ul><ul><ul><li>History of unfulfilled promises </li></ul></ul><ul><ul><ul><li>CASE, EAI or workflow </li></ul></ul></ul><ul><ul><li>Favor short-term benefit </li></ul></ul>
    5. 5. 1. Stakeholder and Potential Conflicts of Interest <ul><li>CEO : responsible for high-level strategic decisions </li></ul><ul><li>Business Unit : driver functional requirement </li></ul><ul><li>CIO </li></ul>
    6. 6. 1. Stakeholder and Potential Conflicts of Interest Cross (Inter)-Enterprise Processes
    7. 7. 2. Organizational Roadmap The organizational SOA road map
    8. 8. 3. Four Pillars for Success(1) <ul><li>4 Main pillars for success of SOA </li></ul><ul><ul><li>Budget </li></ul></ul><ul><ul><li>Project </li></ul></ul><ul><ul><li>Team </li></ul></ul><ul><ul><li>Buddies </li></ul></ul>
    9. 9. 3. Four Pillars for Success(2) <ul><li>Budget </li></ul><ul><ul><li>will be needed to finance one or more initial projects acting as pilot application of SOA </li></ul></ul><ul><ul><li>Compensation for initial overheads caused by SOA </li></ul></ul><ul><ul><ul><li>Employee have to familiarize with new standard and process </li></ul></ul></ul><ul><ul><ul><li>Initial overhead caused by efforts required to increase reusability </li></ul></ul></ul>
    10. 10. 3. Four Pillars for Success(3) <ul><li>Initial Project </li></ul><ul><ul><li>The choice of a suitable project </li></ul></ul><ul><ul><li>Chosen project should be “visible” & less important </li></ul></ul><ul><ul><ul><li>Has to guarantee a significant reuse potential of implemented service </li></ul></ul></ul>
    11. 11. 3. Four Pillars for Success(4) <ul><li>SOA Team </li></ul><ul><ul><li>Support and establish the SOA in the enterprise </li></ul></ul><ul><ul><li>Include </li></ul></ul><ul><ul><ul><li>Design and specification of overall architecture principles </li></ul></ul></ul><ul><ul><ul><li>Standard </li></ul></ul></ul><ul><ul><ul><li>Processes </li></ul></ul></ul><ul><ul><ul><li>Monitoring of actual SOA applications </li></ul></ul></ul><ul><ul><li>Contain “evangelist” </li></ul></ul><ul><ul><ul><li>Explain benefit of the SOA to different departments of the enterprise </li></ul></ul></ul><ul><ul><ul><li>Education on fundamental standards and processes making up the SOA </li></ul></ul></ul><ul><ul><ul><li>Support actual impelmentation of these principles </li></ul></ul></ul>
    12. 12. 3. Four Pillars for Success(5) <ul><li>Backer </li></ul><ul><ul><li>To acquire budget approval and sufficient enterprise-wide awareness to get the SOA off the ground </li></ul></ul><ul><ul><li>Backers and buddies </li></ul></ul><ul><ul><ul><li>Top management : include the SOA in the strategy planning ,covering 3~5 year </li></ul></ul></ul><ul><ul><ul><li>Key business department : Key business function should support SOA </li></ul></ul></ul><ul><ul><ul><li>Key IT management and staff : SOA is primarily a technical issue </li></ul></ul></ul><ul><ul><ul><li>Backers have to sell the SOA to others </li></ul></ul></ul><ul><ul><li>To approach potential supporters </li></ul></ul><ul><ul><ul><li>Who are the target group and key actors? </li></ul></ul></ul><ul><ul><ul><li>What are the 3 main arguments for and against an SOA (per target group,key factor) </li></ul></ul></ul><ul><ul><ul><li>Whose support will be likely? </li></ul></ul></ul><ul><ul><ul><li>Who is to be convinced or overruled? </li></ul></ul></ul>
    13. 13. 3. Four Pillars for Success(5) First Project Backer Management, Business dept, IT staff SOA Team Visible Business but less critical Evangelist has Budget `
    14. 14. 4. An Ideal World(1) <ul><li>To introduce SOA to enterprise </li></ul><ul><ul><li>Whitepapers </li></ul></ul><ul><ul><li>SOA board </li></ul></ul><ul><ul><li>Multi-project management </li></ul></ul><ul><ul><li>Standard process </li></ul></ul><ul><ul><li>Support of all actors </li></ul></ul>
    15. 15. 4. An Ideal World(2) <ul><li>White papers </li></ul><ul><ul><li>“ Why” and “How” </li></ul></ul><ul><ul><li>Strategy white paper </li></ul></ul><ul><ul><ul><li>Explain the overall goal of SOA and its perspective over the next three to five years </li></ul></ul></ul><ul><ul><li>Business white paper </li></ul></ul><ul><ul><ul><li>Business benefits expected from the introduction of an SOA </li></ul></ul></ul><ul><ul><ul><li>ROI </li></ul></ul></ul><ul><ul><li>Technology white paper </li></ul></ul><ul><ul><ul><li>Technological issues involved in implementing the SOA </li></ul></ul></ul><ul><ul><ul><ul><li>How integration of SOA with the existing technological infrastructure is envisaged. </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Special platform – eg ESB </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Repository structure </li></ul></ul></ul></ul>
    16. 16. 4. An Ideal World(3) <ul><li>SOA Boards </li></ul><ul><ul><li>Organizational entity responsible for making a technological vision work in every day life. </li></ul></ul><ul><li>Multi-project management </li></ul><ul><ul><li>SOA project is independent on each other project </li></ul></ul><ul><ul><li>Coordinate the development of each project team </li></ul></ul><ul><li>Standard processes </li></ul><ul><ul><li>Which is business process – ex) ISO9000 </li></ul></ul><ul><ul><li>How new application projects should proceed to make sure that the enterprise’s SOA principles are adhered to </li></ul></ul><ul><ul><li>Can based on standard process – ISO9000, 6 Sigma </li></ul></ul>
    17. 17. 4. An Ideal World(4) <ul><li>Include all relevant actors </li></ul><ul><ul><li>Management, IT depart, business department and admin </li></ul></ul><ul><ul><li>Avoid temptation to choose “new people for a new technology” </li></ul></ul>
    18. 18. 4. An Ideal World(5) <ul><li>SOA Specifics </li></ul><ul><ul><li>Service contracts </li></ul></ul><ul><ul><ul><li>Most obvious starting point for standardization </li></ul></ul></ul><ul><ul><ul><li>Describe and specify services </li></ul></ul></ul><ul><ul><li>Repository </li></ul></ul><ul><ul><ul><li>All including Non-IT should perceive it as a useful tool </li></ul></ul></ul><ul><ul><ul><li>Special team is needed to manage repository. (SOA Team) </li></ul></ul></ul>
    19. 19. 5. Realworld example <ul><li>Failure </li></ul><ul><ul><li>Launch postponed, scope creep, obsolete technology </li></ul></ul><ul><ul><li>Why ? </li></ul></ul><ul><ul><ul><li>Avoid technology Focus </li></ul></ul></ul><ul><ul><ul><li>Start small. [ tried to start after build all of infra structure ] </li></ul></ul></ul><ul><li>Success Story </li></ul><ul><ul><li>Bottom-up approach : start from small pilot project. </li></ul></ul><ul><ul><ul><li>Balanced between business needs and technological features </li></ul></ul></ul><ul><ul><li>Business team and Dev team allocated budget to the pilot and budget. </li></ul></ul><ul><ul><li>Special team monitored compliance with the SOA standards and resuability </li></ul></ul>
    20. 20. 6. Recommendations for the SOA Protagonist <ul><li>Solid foundation – 4 Pillars for SOA </li></ul><ul><li>Establish processes, structures and standards </li></ul><ul><li>Enforce substantial change </li></ul>
    21. 21. Questions?

    ×