1 / 74

DevOps from the Ground Up

What if you had free reign to shape the way that developers and operations worked? What would it look like? What challenges would you have? What do you focus on in leading a deep DevOps culture from the ground up? We'll aim to answer all of these questions by sharing a case study where we established a strong DevOps culture to support Continuous Delivery of software into production.<br><br>Presented at GoTo Berlin 2013.<br><br>http://gotocon.com/berlin-2013/presentation/DevOps from the Ground Up

thekua
Télécharger la présentation

DevOps from the Ground Up

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DevOps from the Ground Up @patkua

  2. DevOps from the Ground Up @patkua

  3. @patkua works for and is author of

  4. develops

  5. helps with

  6. My story ...

  7. DevOps What is

  8. DevOps I do not think it means what you think it means

  9. Dev Ops

  10. Dev Ops DevOps!!!

  11. Dev Ops

  12. Dev Ops “We know what DevOps is”

  13. Ops

  14. Ops “A system to replace all systems” “Push button environments” “We know what developers want”

  15. Ops 9+ months 6+ person team

  16. Ops 9+ months 6+ person team Machines on demand but not in a state for development teams FAIL

  17. Dev Ops “We know what DevOps is”

  18. Dev “We’ll use puppet” “Deployment scripts in ruby” “We know what operations want”

  19. Dev 2+ months automated deploy into test

  20. Dev 2+ months automated deploy into test production on windows operations want a UI FAIL

  21. Dev Ops

  22. Dev Ops A culture and mindset for collaborating between developers and operations

  23. Dev Ops Tools Automation Access rights Teams

  24. Dev Ops Communication Tools Understanding Automation Integration Access rights Relationships Teams

  25. What we set out to do What we did Background What we learned

  26. 14+ months

  27. BI CMS Website Platform New CRM Call centre Recommendations

  28. 16+ programme streams

  29. Team Size : ~ 25 people

  30. “Can we have 20 developers start on day one?”

  31. 4 Product Managers

  32. IT Field of Project Managers

  33. What we set out to do

  34. Practices Practices Principles Principles

  35. “Develop systems, not software” Ben Butler Cole

  36. High Lottery Factor

  37. Why What 1st 2nd

  38. Both sets of interests discussed

  39. Continuous Improvement

  40. Nailed it

  41. What we set out to do What we did

  42. Team Planning Prod Dev Stream Dev Stream

  43. Our practice: Sequential standups

  44. “Operations” Our practice: Pairing “Development”

  45. “Operations” Our practice: Weekly rotation “Development”

  46. “Operations” “Development”

  47. Team Planning

More Related