Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

2019-05-15 How we killed DevOps by creating a dedicated DevOps team

135 Aufrufe

Veröffentlicht am

2019-05-15 DevOpsDays Zurich https://devopsdays.org/events/2019-zurich

In the early days of Netguru, we were a bunch of developers and didn’t even think of having a dedicated ops role - life was simple and easy. The company grew, so did our requirements and challenges, and that’s why we’ve decided to change this by introducing The DevOps Team. That’s also how we’ve entered a very dangerous path with a lot of obstacles related to technology, people, and culture.

This presentation is about real scenarios which we’ve encountered and the way we handled them. This is a story about money, expectations, tickets, sweat, and long hours spent making everybody happy. If you’re thinking of hiring a “DevOps Specialist”, then this talk is just for you. Don’t wake up one day and realise that there’s a team in your organisation which takes your focus and energy in the wrong direction.

Veröffentlicht in: Leadership & Management
  • Als Erste(r) kommentieren

2019-05-15 How we killed DevOps by creating a dedicated DevOps team

  1. 1. How we killed DevOps by creating a dedicated DevOps team Adam Nowak
  2. 2. 🌃
  3. 3. 😤
  4. 4. 📳
  5. 5. 🔥
  6. 6. 👍
  7. 7. 🏁
  8. 8.
  9. 9. 👶
  10. 10.
  11. 11. Hello Zurich! Grüezi mitenand!
  12. 12. Hello Spreitenbach! Grüezi mitenand!
  13. 13. Hello DevOps friends! Grüezi mitenand!
  14. 14. _ How did we kill DevOps?
  15. 15. Let’s go back in time
  16. 16. Pre-DevOps team era Pre-D evO psteam
  17. 17. Pre-DevOps team era •Small web-dev agency •Simple infrastructures •No dedicated "ops" role •Developers manage servers and deploy on their own
  18. 18. Developer manage servers… •Small community •Open meetings •Common tools & best practices •Part-time Ops
  19. 19. DevOps definition v1 People who can do servers and update them via scripts and they automate things.
  20. 20. Challenges 🤝+ 🤯⚙
  21. 21. Things evolve •We need someone to take us through the cloud & container journey •We want to automate everything •There is more "heavy DevOps" to handle
  22. 22. We need him!
  23. 23. Create A proper Team
  24. 24. DevOps Team Pre-D evO psteam D evO psteam
  25. 25. DevOps delivers 📦☁ 0♾
  26. 26. Growth happens
  27. 27. 23456🧟89 :;<=>?@ABCDEFGHIJKL👩NO PQRSTUVWXYZ[🧓^_`a🎅cdefghi👷klm nopqr👧tuv🧑xyz{|}~•€•‚ƒ„…†‡ˆ‰Š‹ Œ•Ž👵•‘’“”•–🧙˜™š🧜œ•žŸ ¡¢£¤¥¦§¨👳 ª«¬-®¯°±²³🤵µ¶·🦹¹º»¼👦¾¿ÀÁÂÃÄÅÆÇ ÈÉ👨ËÌÍÎÏÐÑÒÓ🧕ÕÖ×ØÙÚÛ Ü💂Þßàáâ👸äå æçèéêëìíîïðñòóôõö÷øù🧒û👴ýþÿ!"#$ %&'()*+,👲./0123456789:;<=>?ê@A BCDEFG🤶IJKLMNOPQR🧚TUVWXYZ[]^_ `abcdefghijklmnopqrstuvwxy🧛{|🤴 ~•€•‚ƒ„…🕵👱ˆ‰Š‹Œ🧔Ž••‘’0“”•–—˜™š ›œ•ž🦸 ¡¢£¤¥¦🧞¨©ª«ó¬-®¯👰±²³´µ👮¿ ŒucžXr{²×Ф©Ù „🧟˜·ª👨>-¸🤵👸Ó🧓 •œ[kHi¹Þ¡Qa;® +=qu¯j‘ñ|b³
  28. 28. Something is not right…
  29. 29. DevOps team ó¶ÿêW
  30. 30. Something is not right… This is what devops do! ☝ I’m here to do dev stuff! 😤 I don’t know how to… » The checklist doesn’t work ☹ I can’t access the server 😡 I’m getting crazy about waiting for 3-4 weeks for simple tasks! 🕰 🛑
  31. 31. 🤔💩❓
  32. 32. _ What’s going on?
  33. 33. We can’t keep up with work
  34. 34. Centralisation Project Project Project Project Project Project Project Project Project Project Project Project Project Project Project Project Project Project Improvement DevOps Project Project Project 😡 😠 🤬 👎 🔥 😱
  35. 35. _ The result?
  36. 36. The Ops knowledge among the team decreases
  37. 37. The tools we created are for Ops, not Devs
  38. 38. Everything is maintained from one central place
  39. 39. The tension between teams becomes an issue
  40. 40. Let’s hire More DevOps engineers!
  41. 41. Not so easy
  42. 42. Overtime is the new normal
  43. 43. On-call is just yet another shift
  44. 44. Business landscape changes 💰👔 💯☝
  45. 45. At the same time the team needs 🙏🤝 🧯🛠
  46. 46. State of DevOps •There’s a huge demand for the DevOps services •DevOps is the bottleneck
  47. 47. 🔥 🚒🔥 🧯🔥 🔥 🔥 🔥 🔥 🔥 🔥🔥🔥 🔥 🔥 🔥 🔥 🔥
  48. 48. No one is happy
  49. 49. 💩❗
  50. 50. Desperate times, desperate measures
  51. 51. #devops-wartime Pre-D evO psteam D evO psteam #devops-w artim e
  52. 52. Photo by Shane Rounce on Unsplash All hands on deck
  53. 53. Cooperation with other departments Photo by Quino Al on Unsplash
  54. 54. Daily meetings & status updates Photo by Thomas Drouault on Unsplash
  55. 55. Communication during #devops-wartime ⛺🔥 ✅
  56. 56. Focus!
  57. 57. Wartime gave us •Sense of urgency •Cross-company collaboration and engagement •Possibility of doing things differently •Focus
  58. 58. Positive feedback! I really appreciate the efforts to reorganise structure and processes in the DevOps team. DevOps: Guys are doing massive overtime, their processes are a to be cleaned-up - I'm really hoping they will figure this out in upcoming months, fingers crossed! I think that the situation between PM and DevOps goes in the right direction, recent news about the reorganisation are very encouraging!
  59. 59. DevOps enlightenment Pre-D evO psteam D evO psteam #devops-w artim e D evO psenlightenm ent
  60. 60. The "AHA!" moment
  61. 61. Slack conversation with my friend Bartosz
  62. 62. DevOps?
  63. 63. DevOps!
  64. 64. HTTPS://AWS.AMAZON.COM/DEVOPS/WHAT-IS-DEVOPS/ DevOps definition v2 Combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity.
  65. 65. DevOps culture Pre-D evO psteam D evO psteam #devops-w artim e D evO psenlightenm ent D evO psculture
  66. 66. CALMSDiamond Edwards & John Willis Culture Automation Lean Measurement Sharing
  67. 67. Be aware of DevOps teams
  68. 68. We need to work together
  69. 69. Good change takes time
  70. 70. Continuous *
  71. 71. DevOps is dead Long live DevOps!
  72. 72. DevOps is a culture, a movement, a philosophy
  73. 73. DevOpsDays lunch ☕ ☕ ☕ 🍪 ☕ 🍽
  74. 74. Thanks! Adam Nowak Development Process Practice Lead @lubieniebieski | adam@netguru.com

×