Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Foundation for accelerating digital development—Two-speed IT

1,764 views

Published on

The rapid growth in mobile, big data, and cloud technologies has profoundly changed market dynamics in every industry, including financial services, driving the convergence of the digital and physical worlds, and changing customer behavior.

Published in: Technology
  • Be the first to comment

Foundation for accelerating digital development—Two-speed IT

  1. 1. Two-Speed IT & APIs Using APIs to build an agile digital business platform Presented by Ed Anuff, SVP Product Strategy @ Apigee February 10, 2016
  2. 2. @edanuff Ed Anuff
  3. 3. What is “2-Speed IT”? 3
  4. 4. Two-Speed IT Systems of Record Systems of Engagement Partner Apps Employee Apps Consumer Apps Insights ESB / Integration ERP DatabaseCRM Data Lake Data Warehouse
  5. 5. What about “Bimodal” IT? 5
  6. 6. 6 Gartner’s Bimodal IT Source: Gartner- Drive Digital Business Using Insights From Symposium's Analyst Keynote
  7. 7. 7 Pace Layering
  8. 8. 8
  9. 9. 9 Bimodal IT and Pace Layering Systems Of Engagement Systems Of Differentiation Systems Of Record Mode 1 Mode 2 + - Change - + Governance Source: Gartner
  10. 10. 10 Decentralizing Excellence Source: Forrester - The Digital Business Imperative, 2014, Fenwick, Gill
  11. 11. 11 Impact of Two-Speed IT
  12. 12. Do these phrases describe your IT organization? Outside in, Cloud-first, Mobile-centric 12 Drive pace that others can’t match Source: Apigee Institute survey of 800 IT decision makers at companies with over $500M in annual revenue, 8 countries, 25 industries Yes (12%) No (88%) 12X more likely to greatly exceed expectations for speed building & delivering apps 7X more likely to fail to meet expectations for speed with apps
  13. 13. Are there only 2 speeds? 13
  14. 14. 14
  15. 15. No, the point is there’s more than 1… 15
  16. 16. 16 Source: Simon Wardley
  17. 17. How are APIs relevant to 2- Speed IT? 17
  18. 18. Two-Speed IT With APIs Systems of Record Systems of Engagement Partner Apps Employee Apps Consumer Apps Insights ESB / Integration ERP DatabaseCRM Data Lake Data Warehouse API Gateway Tier
  19. 19. 19 Software-defined Application Services Source: Gartner- Application Architecture For Digital Business, Anne Thomas, Yefim Natis, Ross Altman
  20. 20. 20 Software-defined Application Services Source: Gartner- Application Architecture For Digital Business, Anne Thomas, Yefim Natis, Ross Altman
  21. 21. 21
  22. 22. Discover Deploy Decide
  23. 23. Discover Deploy Decide Speed
  24. 24. Discover Deploy Digital asset Decide
  25. 25. Discover Deploy Digital asset Digital experience Decide
  26. 26. Discover Deploy Digital asset Digital experience Digital interaction Interaction data Decide
  27. 27. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Decide
  28. 28. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Dev time & attention Decide
  29. 29. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide
  30. 30. 30 APIs are the foundation of two-speed IT
  31. 31. 31 An API platform is table stakes for the new pace of business APIs are the foundation of two-speed IT
  32. 32. 32 “[The API program] is an architectural choice one makes for speed.” John Donovan, Sr. EVP, Technology and Network Ops, AT&T
  33. 33. 33 …[A] digitized platform is table stakes for rapid innovation….if [a new app] can’t be integrated onto the platform, you end up with data that can’t easily be analyzed and transactions that take time to process…. With a digitized platform and its associated APIs, [it] can plug in to the platform and immediately start delivering service… Weill, Woerner, Ross, “Five Propositions for Thriving with Digital Disruption,” MIT CISR “[The API program] is an architectural choice one makes for speed.” John Donovan, Sr. EVP, Technology and Network Ops, AT&T
  34. 34. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide APIs Devs love
  35. 35. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide APIs Devs love SOE APIs
  36. 36. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide APIs Devs love SOE APIs Data @ scale
  37. 37. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide APIs Devs love SOE APIs Data @ scale Real time monitoring
  38. 38. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Adaptive algorithms Dev time & attention Decide APIs Devs love SOE APIs Data @ scale Real time monitoring Reporting/ alerts
  39. 39. Discover Deploy A/B test results Fail/scale decision Digital asset Digital experience Digital interaction Interaction data Dev time & attention Decide APIs Devs love SOE APIs Data @ scale Real time monitoring Reporting/ alerts Real time analytics Adaptive algorithms
  40. 40. 40 Large enterprises should create a central integration competency center to reduce the time and cost required to integrate application systems. One of the most common problems encountered by integration centers is the tendency for application developers to bypass the enterprise grid and solve integration problems using conventional, point-to-point interfaces and traditional technology. There is no easy way to prevent this problem. Roy Schulte, Gary Long, Gartner Group The Role of the Integration Competency Center, 2002
  41. 41. All teams will henceforth expose their data and functionality through service interfaces. Teams must communicate with each other through these interfaces. There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back- doors whatsoever. The only communication allowed is via service interface calls over the network…All service interfaces, without exception, must be designed from the ground up to be externalizable. That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. Anyone who doesn’t do this will be fired. Jeff Bezos, CEO, Amazon, “Yegge Rant,” 2002 41 Large enterprises should create a central integration competency center to reduce the time and cost required to integrate application systems. One of the most common problems encountered by integration centers is the tendency for application developers to bypass the enterprise grid and solve integration problems using conventional, point-to-point interfaces and traditional technology. There is no easy way to prevent this problem. Roy Schulte, Gary Long, Gartner Group The Role of the Integration Competency Center, 2002
  42. 42. Thank You 42

×