Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

DevOps & Cloud-Native for Enterprise Architects Not Dead Yet

95 visualizaciones

Publicado el

Pivotal Paris 2019: DevOps & Cloud-Native for Enterprise Architects Not Dead Yet

Publicado en: Software
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

DevOps & Cloud-Native for Enterprise Architects Not Dead Yet

  1. 1. DevOps & Cloud-Native for Enterprise Architects Not Dead Yet July, 2019 @cote 1
  2. 2. 2 First, what is “enterprise architecture”?
  3. 3. 3 Source: Enterprise Architecture as Strategy, Jeanne W. Ross, Peter Weill, David Robertson, 2006.
  4. 4. 4
  5. 5. 5Source: “The New CIO: Leading IT the Mark Schwartz Way,” DOES London, 2018. The CIO is the enterprise architect and arbitrates the quality of the IT systems in the sense that they promote agility in the future. The systems could be filled with technical debt but, at any given moment, the sum of all the IT systems is an asset and has value in what it enables the company to do in the future. The value is not just in the architecture but also in the people and the processes. It's an intangible asset that determines the company's future revenues and costs and the CIO is responsible for ensuring the performance of that asset in the future. “
  6. 6. 6 The problem
  7. 7. 7 If I’m doing 8 or 15 releases a week, how am I going to get through all those CABs?” “
  8. 8. 8
  9. 9. 11Sources: "Building a Brand Around a Technology and Cultural Transformation," Matt Curry, Sep. 2016.
  10. 10. 12 Leading change
  11. 11. 13 Mobile payments Mortgage application Mortgage approval Bill pay Transfers 🤓 🤓 Private or public IaaS "👔$Culture, process, methodology, governance, compensation, etc. IT Leadership, EAs, etc. Platform Engineers Product teams Corporate strategy, revenue goals, mission, etc. 💼🤑🏭🏢 🏛 🌥 ☁ “The Business”
  12. 12. 14
  13. 13. Beyond 10 ways to make coffee: gardening “culture” ● Create a culture of innovation, risk taking, and focusing on people (“users”) ● Give product teams autonomy, trust, and voice ● Establish trust by doing what you say, delegating, and celebrating failurelearning. ● Feedback loop: surveys (ENPS), silence, churn, results. ● Giving feedback: OKRs, praising process & stories, not just schedule 15More: "Creating a DevOps culture, whatever that means".
  14. 14. 16 Gardening teams
  15. 15. Closer to a product organization… 17 Mobile payments Mortgage application Mortgage approval Bill pay Transfers
  16. 16. 18
  17. 17. 19
  18. 18. 20 Gardening microservices (and the before times)
  19. 19. 21
  20. 20. 22Source: @AreasAbandoned. 22
  21. 21. 23 Gardening platform & Tools
  22. 22. 24Source: Presentation at SpringOne Platform, Sep 2018. [I]f you say to your team that 'when you build it you also run it,’ you cannot do that with a consolidated environment. You cannot say to a team 'you own that stuff, and by the way somebody else can also break it.'" Vincent Oostindië, Rabobank “
  23. 23. Choose, govern, and garden the right platform 25 Source: CF Summit Europe 2018, Vincent Oostindië, Rabobank.
  24. 24. Enterprise architecture as code 26Sources: Enterprise Architecture as Strategy, Jeanne W. Ross, Peter Weill, David Robertson, 2006; Ranji Narine at SpringOne Platform 2017.
  25. 25. 27
  26. 26. 28 The left overs: • The Platform as a Product team • Gardening technical decisions & services • Internal marketing & training
  27. 27. 29 @cote | cote@pivotal.io http://cote.io/books

×