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.

Adopting DevOps @ Scale: Lessons learned at Hertz, Kaiser Permanente and lBM

873 visualizaciones

Publicado el

DevOps has become a major enabler of business innovation that can drive digital transformation at an enterprise level if done well. Challenges remain, however. Crossing the chasm from successful DevOps pilots with "two-pizza" teams to full enterprise adoption, including cultural transformation, best practices and tools remains a challenge.

Join Alan Shimel as he hosts a panel discussion with Hertz' John LaFreniere, Kaiser Permanente's Raghunath Raman and IBM's Sanjeev Sharma on how traditional enterprises are accelerating innovation by adopting DevOps practices at scale across their organizations.

Find out how:

- Hertz is accelerating transformation of their platforms, business process and operating models with Cloud, DevOps and Agile.

- Kaiser Permanente is managing the cultural, process and integration challenges of multi-speed IT.

- IBM has embarked on a DevOps transformation that has engaged over 10,000 developers already -- including becoming one of the world's largest users of GitHub Enterprise.

Watch to learn how to assess your organization’s readiness for scaling DevOps, and to identify next steps.

Publicado en: Software
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Adopting DevOps @ Scale: Lessons learned at Hertz, Kaiser Permanente and lBM

  1. 1. © 2016 IBM Corporation 1 Adopting DevOps @ Scale: Lessons learned at Hertz, Kaiser Permanente and lBM November 29th, 2016
  2. 2. © 2016 IBM Corporation 2 Sanjeev Sharma CTO, DevOps Technical Evangelist, Distinguished Engineer, IBM Raghunath Raman Director - Digital APIs and Integration Delivery, Kaiser Permanente Speakers John LaFreniere Vice President of Global IT Architecture, Hertz Corporation Alan Shimel Moderator, Editor-in- Chief, DevOps.com
  3. 3. 4Page  Technology debt of legacy systems has created the need for Greenfield builds of new systems versus traditional upgrade / evolve methods  Move to Cloud/SaaS to reduce/eliminate dependence on existing data centers  ConfigOps – unleash DevOps at a macro/ enterprise scale through SaaS, PaaS, and cloud adoption Hertz has been in business for nearly 100 years Hertz Enterprise DevOps Strategy 4
  4. 4. 5Page DevOps Journey (top-down?) DevOps and cloud tend to be grassroots initiatives  At Hertz, the decision was driven from the CIO Setting the strategy is easy when compared to resetting the culture of an entire company  Must be driven by highest levels of management as a company priority 5
  5. 5. 6Page  Cloud isn’t magic – it takes resources, planning and effort. You must educate leadership early and often avoid misperceptions  Avoid a plan that enables getting stuck in a hybrid state of both traditional data centers and cloud with no end in sight Challenges for Enterprise DevOps 6
  6. 6. 7 7Page© 2016 IBM Corporation  10.6+ Million members  38 Hospitals  626 Medical offices  18,652 Physicians  51,010 Nurses  194,294 Employees (technical, Administrative, clerical and caregivers) Data from Sep 2016 A few statistics of member usage on digital channels (Dec 2014)  Visits to kp.org (including visits to m.kp.org) : 162M  Total registered members : 4.89M  Test results released online : 78M  Test results viewed online : 37.4M  Emails sent to doctors and other providers : 20M  Prescription refills submitted online : 17.5M  Appointments booked online : 4.2M  Kaiser Permanente mobile app downloads : 1.1 million 7
  7. 7. 8 8Page© 2016 IBM Corporation Lower Cost Higher Productivity Fast Time to Market Maximize Re-use Why DevOps? Challenges Benefits 8
  8. 8. 9 9Page© 2016 IBM Corporation Behavioral, process, and technology implications for DevOps @ scale Implications Behavioral Implications  Embrace agile for small incremental releases  Establish a culture that encourages and values continuous feedback  Whole team (e.g., business, development, testing, operations) ownership of solution performance  Increased collaboration across Business and IT, and within IT  Establish a culture of quality  Think automation Process Implications  Must support end-to-end DevOps planning  Establish 100% automation at the infrastructure, middleware, application/deployment layers  Create a sense and respond processes enabled by predictive data analysis & application instrumentation  Improve capacity planning process  Measure process performance Technology Implications  Remove environment and deployment activities from the developer  Create automated testing and test data  Establish collaborative life cycle management  Standardize monitoring tools across environments  Create re-usable scripts and deployment tools  Create pattern-based provisioning and virtualized services  Collection of metrics 9
  9. 9. © 2016 IBM Corporation 1010 Development SCM Build Package Repo Deploy Development SCM Build Package Repo Deploy Development SCM Build Package Repo Deploy Development SCM Build Package Repo Deploy Test Stage Production Application N Application C Application B Application A Enterprise Release Agile/Innovation Edge Rapid Delivery for Innovation • Agile • Antifragile • Experimentation • New and Innovative • Hybrid Cloud • PaaS Industrialized Core Deliver at regular cadence • Waterfall -> Agile • Stability • Predictability • Lean Delivery pipeline • Core and Legacy Hybrid Infrastructure – Physical, Cloud • IaaS/PaaS Business Capability Delivering a Business Capability: Hybrid Applications, Hybrid Platforms, Hybrid Teams 10
  10. 10. 11Page© 2016 IBM Corporationhttps://www.ibm.com/devops/method/content/architecture/architecture_devops Data & Analytics Hybrid Microservices Mobile IoT Web App Use DevOps practices, architectures and toolchains to build different types of applications. Integrated view of DevOps practices, architectures & toolchains 11
  11. 11. © 2016 IBM Corporation 12© 2016 IBM Corporation 12 The DevOps Optimization and Innovation Workshop  Review the ‘waste’ in the current state (Value Stream Mapping) 1. Business goals, IT goals, current initiatives 2. Artifacts 3. Stakeholders 4. Environments 5. Repositories 6. Roles / Organization 7. Metrics 8. Security 9. Culture  Prioritize challenges to be mitigated  Create a first pass at a DevOps Adoption roadmap The whiteboard 12
  12. 12. © 2016 IBM Corporation 13© 2016 IBM Corporation 13 Innovate faster by accelerating software delivery across hybrid environments Transformed from 18- month cycle times to delivering a complete mobile solution in just five months—with 3-week update cycles Improve customer engagement by shortening feedback loops Generated 1,000 items of feedback on new mobile app in 2 weeks. Reduced implementation time by 90-95% Create a culture of continuous improvement and trust Reduced critical defects by 80% over the last three years. 90% on-time delivery versus 60% previously Eliminate error-prone manual steps and speed up the release process Reduced time required for software releases by 99%. Cost avoidance of more than US$2.3M per year for one app. DevOps accelerates digital transformation with standardization and automation 13
  13. 13. © 2016 IBM Corporation 14 Next Steps  Video: DevOps and Open Technologies - Innovate Like a Startup, Scale for the Enterprise  Video: IBM DevOps Video Chat with Gene Kim and DOES16 speakers  Video: IBM InterConnect 2016: Raghunath Raman on Kaiser Permanente's DevOps Journey  Check out the IBM Bluemix Garage Method for guidance on your DevOps journey, including methods, learning labs and reference architectures.  Learn how IBM Bluemix Continuous Delivery helps you accelerate your transformation with integrated tools
  14. 14. © 2016 IBM Corporation 15 InterConnect 2017, March 19-23 in Las Vegas Registration for InterConnect 2017 is open! http://ibm.com/interconnect
  15. 15. © 2016 IBM Corporation 16 Thank You!

×