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 transformations for I.T.A.K.E 2018

524 views

Published on

SysAdmins are obsolete, we need more DevOps engineers! Or do we? Why technology X is not what you need right now? Why ignoring skills that are already present in the team may be a huge risk? Why everything-as-code is an effective approach? Why not investing in team member education may be very destructive? Why not having time is a bad excuse for not automating? Why process improvement effects may not be observable immediately? Why cost of automation sometimes is higher than the time invested in writing the scripts?

Published in: Technology
  • Be the first to comment

  • Be the first to like this

DevOps transformations for I.T.A.K.E 2018

  1. 1. 01
  2. 2. 02
  3. 3. "DevOps" tools 03
  4. 4. Tools 04
  5. 5. More tools 05
  6. 6. Even more tools 06
  7. 7. Is this the best stack? 07
  8. 8. Does this help? 08
  9. 9. Or this? 09
  10. 10. Ocean of tools! 10
  11. 11. But... 11
  12. 12. DevOps is not about tools! 12
  13. 13. Or is it? 13
  14. 14. History 14
  15. 15. Tools and weapons 15
  16. 16. Tools and weapons 16
  17. 17. Tools and weapons 17
  18. 18. We use tools to protect our culture!18
  19. 19. Tools vs Culture 19
  20. 20. Technology vs Organization20
  21. 21. Healthy lifestyle 21
  22. 22. Start running 22
  23. 23. Broken leg! 23
  24. 24. Regret 24
  25. 25. Running does not work! 25
  26. 26. Running is not for me! 26
  27. 27. Running is for healthy people!27
  28. 28. Well... 28
  29. 29. Combination of things Just walking instead of running Different diet More sleeping time Mix activities Reduce stress (peace of mind) Find a trainer/mentor • • • • • • 29
  30. 30. Tools vs Culture 30
  31. 31. Dialogues 31
  32. 32. 32
  33. 33. 33
  34. 34. 34
  35. 35. 35
  36. 36. Broken communication 36
  37. 37. Rigid structure 37
  38. 38. 38
  39. 39. We still believe in magic!39
  40. 40. Lack of culture? 40
  41. 41. Lack of tooling? 41
  42. 42. 2001 42
  43. 43. Agile 43
  44. 44. Agile principles Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan • • • • 44
  45. 45. 2003 45
  46. 46. 46
  47. 47. Mary Poppendieck 47
  48. 48. Lean Software Development48
  49. 49. Lean principles Eliminate waste Amplify learning Decide as late as possible Deliver as fast as possible Empower the team Build integrity in See the whole • • • • • • • 49
  50. 50. 2008 50
  51. 51. 51
  52. 52. Andrew Clay Shafer 52
  53. 53. Infrastructure is Code 53
  54. 54. 54
  55. 55. Patrick Debois 55
  56. 56. Agile Infrastructure 56
  57. 57. DevOps 57
  58. 58. DevOps DevOps is a human problem. “ 58
  59. 59. What's DevOps? 59
  60. 60. Wikipedia DevOps aims at shorter development cycles, increased deployment frequency, and more dependable releases, in close alignment with business objectives. “ 60
  61. 61. 2010 61
  62. 62. 62
  63. 63. John Willis 63
  64. 64. C.A.M.S Culture Automation Measurement Sharing • • • • 64
  65. 65. 2013 65
  66. 66. 66
  67. 67. Gene Kim 67
  68. 68. The 3 ways of DevOps 68
  69. 69. The first way 69
  70. 70. The second way 70
  71. 71. The third way 71
  72. 72. 2011 72
  73. 73. 73
  74. 74. Jez Humble 74
  75. 75. CD principles Build quality in Work in small batches Computers perform repetitive tasks, people solve problems Relentlessly pursue continuous improvement Everyone is responsible • • • • • 75
  76. 76. 2017 76
  77. 77. GitOps! 77
  78. 78. The single source of truth78
  79. 79. Ops by pull request 79
  80. 80. Who do we need? 80
  81. 81. T-shaped people 81
  82. 82. T-shaped people 82
  83. 83. How do we plan? 83
  84. 84. 84
  85. 85. Gene Kim 85
  86. 86. Unplanned work 86
  87. 87. Unplanned work 87
  88. 88. Unplanned work 88
  89. 89. Unplanned work 89
  90. 90. 90
  91. 91. Dominica DeGrandis 91
  92. 92. Time thieves 92
  93. 93. Reduce WIP 93
  94. 94. More No! 94
  95. 95. How should we work together?95
  96. 96. 96
  97. 97. Mathew Skelton 97
  98. 98. DevOps Topologies 98
  99. 99. Type 1: Dev and Ops Collaboration 99
  100. 100. Type 2: Fully Shared Ops Responsibilities 100
  101. 101. Type 3: Ops as Infrastructure-as-a- Service 101
  102. 102. Type 4: DevOps as an External Service 102
  103. 103. Type 5: DevOps Team with an Expiry Date 103
  104. 104. What should we use? 104
  105. 105. 105
  106. 106. Neal Ford 106
  107. 107. Innovation curve 107
  108. 108. Technology radar 108
  109. 109. Rings Hold Assess Trial Adopt • • • • 109
  110. 110. Quadrants 110
  111. 111. Radar example 111
  112. 112. Radar example 112
  113. 113. Future is here! The future is already here ? it's just not very evenly distributed. William Gibson “ 113
  114. 114. Where do we aim? 114
  115. 115. Where is the industry going?115
  116. 116. 116
  117. 117. Simon Wardley 117
  118. 118. Maps Visual Context Position, anchor and movement Components • • • • 118
  119. 119. Maps Navigation Learning Strategy Situational awareness • • • • 119
  120. 120. Maps 120
  121. 121. Are you ready for CN? 121
  122. 122. Final words Directions and planning as well as progress should be visible (radars, maps, boards) VCS repos are the only source of truth (CD + GitOps) Pipelines handle all aspects of software delivery (CD + GitOps) Tools do not matter that much, but use them to enforce your culture! • • • • 122
  123. 123. Everything is code! 123
  124. 124. IT is code! 124
  125. 125. We are all contributors! 125
  126. 126. We are all collaborators! 126
  127. 127. Thank you! 127
  128. 128. Kahoot! 128
  129. 129. 129

×