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.

DevOps: From Adoption to Performance

1,285 views

Published on

Organizations like Google, Amazon, Facebook, and Netflix employ DevOps practices to deploy code into production hundreds, or even thousands, of times per day, while providing world-class availability, reliability, and security. In contrast, many organizations struggle to release every nine months.

But DevOps isn't just for the Unicorns.

Gene Kim, co-author of The Phoenix Project and the upcoming DevOps Cookbook, shares:
• How you can replicate the DevOps practices and outcomes of the so-called “Unicorns”
• The top lessons learned in his study of high-performing technology organizations
• How you can apply these lessons at your company

Register for “DevOps: From Adoption to Performance” and learn how even large, complex organizations across almost every vertical are using DevOps practices to replicate the technology and performance feats of the “Unicorns.”

https://info.dynatrace.com/apm_wc_Gene_Kim_webinar_na_registration.html

Published in: Technology

DevOps: From Adoption to Performance

  1. 1. 1 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive DevOps: From Adoption to Performance Tweet your thoughts & questions using #APMLive Gene Kim Co-Author, The Phoenix Project @RealGeneKim Martin Etmajer Sr. Technology Strategist at Dynatrace martin.etmajer@dynatrace.com @metmajer
  2. 2. @RealGeneKim Gene Kim Co-Author, The Phoenix Project @RealGeneKim
  3. 3. @RealGeneKim Agenda  Gene Kim  What is DevOps and the practices that enable them  DevOps adoption in large, complex organizations  Two case studies: CSG and Capital One  Martin Etmajer  The No-War-Room Scenario
  4. 4. @RealGeneKim There Is A Better Way: Google, Amazon, Netflix, Spotify, Etsy, Spotify, Twitter, Facebook…
  5. 5. @RealGeneKim High Performers Are More Agile 30x 8,000x more frequent deployments faster lead times than their peers Source: Puppet Labs 2013 State Of DevOps: http://puppetlabs.com/2013-state-of-devops-infographic
  6. 6. @RealGeneKim High Performers Are More Reliable 2x 12x the change success rate faster mean time to recover (MTTR) Source: Puppet Labs 2013 State Of DevOps: http://puppetlabs.com/2013-state-of-devops-infographic
  7. 7. @RealGeneKim High Performers Win In The Marketplace 2x 50%more likely to exceed profitability, market share & productivity goals higher market capitalization growth over 3 years* Source: Puppet Labs 2014 State Of DevOps
  8. 8. @RealGeneKim The Three Ways
  9. 9. @RealGeneKim The First Way: Flow  Creating single repository for code and environments  All Ops artifacts in version control  Determinism in the release process  Consistent Dev, Test and Production environments, all properly built before deployment begins  Developers checking in code daily, being productive  Automated regression testing  Features being deployed daily without catastrophic failures  Decreased lead time  Faster cycle time and release cadence
  10. 10. @RealGeneKim The Second Way: Feedback  Peer review of code and environment changes  Disciplined automated testing enabling many simultaneous small, agile teams to work productively  Proactive monitoring of the production environment  Defects and security issues getting fixed faster than ever  High trust culture  All groups communicating and coordinating better  Everybody is getting more work done
  11. 11. @RealGeneKim The Third Way: Organizational Learning  Reserve 20% of all Dev and Ops cycles for paying down technical debt  Fearlessly inject faults into the production environment to gain assurance of our resilience  Do everything we can to enable developer productivity  Create organizational learning from our successes and failures, so we can win in the marketplace
  12. 12. @RealGeneKim DevOps Enterprise Summit Learnings
  13. 13. @RealGeneKim DevOps Enterprise: Lessons Learned  On Oct 21-23, we held the DevOps Enterprise Summit, a conference for horses, by horses  Speakers included fifty leaders from:  Macy’s, Disney, Target, GE Capital, Blackboard, Nordstrom, Telstra, US Department of Homeland Security, CSG, Raytheon, IBM, Ticketmaster, MITRE, Marks and Spencer, Barclays Capital, Microsoft, Nationwide Insurance, Capital One, Gov.UK, Fidelity, Rally Software, Neustar, Walmart, PNC, ADP, …
  14. 14. @RealGeneKim The most popular and talked-about presentation at DevOps Enterprise 2014? Mark Schwartz, CIO, US Citizenship and Immigration Services, Department of Homeland Security
  15. 15. @RealGeneKim Observations  They were using the same technical practices and getting the same sort of metrics as the unicorns  Target: 10+ deploys per day, < 10 incidents per month  Capital One: 100s of deploys per day, lead time of minutes  Macy’s: 1,500 manual tests every 10 days, now 100Ks automated tests run daily  Nationwide Insurance: Retirement Plans app (COBOL on mainframe)  Raytheon: testing and certification from months to a day  US CIS: security and compliance testing run every code commit
  16. 16. @RealGeneKim Observations  The transformation stories are among the most courageous I’ve ever heard –  Often the transformation leader was putting themselves in personal jeopardy  Why? Absolute clarity and conviction that it was the right thing for the organization
  17. 17. @RealGeneKim Experiment: Reducing Batch Size By 50% Source: Scott Prugh, Chief Architect, CSG, Inc. And the customer got the feature in half the time!
  18. 18. @RealGeneKim Capital One: DevOpsSec Source: Tapabrata Pal, Capital One
  19. 19. @RealGeneKim
  20. 20. @RealGeneKim “deploys / day” “deploys / day / dev”
  21. 21. @RealGeneKim Want More Learn More? To receive the following:  A copy of this presentation  The 140 page excerpt of The Phoenix Project  The 6 hour excerpt of The Phoenix Project audiobook  Videos and slides from DevOps Enterprise 2014  Information on DevOps Enterprise 2015  Link to the DevOps Audit Defense Toolkit  See early drafts of our upcoming DevOps Cookbook Just pick up your phone, and send an email: To: realgenekim@SendYourSlides.com Subject: devops realgenekim@SendYourSlides.com devops
  22. 22. 22 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Resolve Root-Causes in Minutes with Dev, Test and Ops Martin Etmajer, Senior Technology Strategist @Dynatrace The No-War-Room Scenario
  23. 23. 23 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Do we still need War Rooms?
  24. 24. 24 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive “I’ve muddled over the same log files for weeks sometimes to extrapolate the relationships between different systems [...] before having my eureka moment.” RecklessKelly (Operator) on reddit
  25. 25. 25 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Can we do Better?
  26. 26. 26 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive
  27. 27. 27 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Host Health?
  28. 28. 28 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive
  29. 29. 29 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive
  30. 30. 30 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Transactions Health?
  31. 31. 31 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Relevance?
  32. 32. 32 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive
  33. 33. 33 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Dynatrace Session File
  34. 34. 34 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Get Everyone into a War Room?
  35. 35. 35 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Get Everyone into a War Room? NO!
  36. 36. 36 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Instead?
  37. 37. 37 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Takeaways?
  38. 38. 38 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Takeaways?
  39. 39. 39 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Takeaways?
  40. 40. 40 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive Takeaways?
  41. 41. 41 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive » identified whether it’s been the host, process or transactions » identified which critical business functionality was affected » been able to prioritze the failure and secure evidence » gotten the right people on the same table » taken minutes, not weeks! Awesome! We have...
  42. 42. 42 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive
  43. 43. 43 COMPANY CONFIDENTIAL – DO NOT DISTRIBUTE #APMLive

×