Your SlideShare is downloading. ×
DevOps from the Ground Up
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

DevOps from the Ground Up

7,634

Published on

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 …

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.

Presented at GoTo Berlin 2013.

http://gotocon.com/berlin-2013/presentation/DevOps%20from%20the%20Ground%20Up

Published in: Technology, Business
1 Comment
39 Likes
Statistics
Notes
  • Maybe the video would be more helpful . The slides give an idea of what did not work . But does not give an idea of what worked
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
7,634
On Slideshare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
495
Comments
1
Likes
39
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

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. What is DevOps
  • 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 Tools Communication Automation Understanding Access rights Integration Teams Relationships
  • 25. What we set out to do Background What we did What we learned
  • 26. 14+ months
  • 27. BI CMS Website CRM Call centre Ne w rm fo at Pl 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 1st What 2nd
  • 38. Both sets of interests discussed
  • 39. Continuous Improvement
  • 40. Nailed it
  • 41. What we set out to do What we did
  • 42. Prod Team Planning 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
  • 48. “Operations” Our practice: One lead per team “Development”
  • 49. Logical Architecture
  • 50. Physical Architecture Our practice: Everyone knows what production looks like
  • 51. Developers working on these as well Dependency
  • 52. Ready for analysis Ready for Dev In Analysis Ready for QA In Dev Ready for Sign Off In QA Our practice: Released Ready for Release Visibility of *all* activities
  • 53. PRODUCTION ACCESS? Y U NO KEEP IT SEPARATE? Pipelines to Production
  • 54. Production-like environment with
  • 55. Tech Lead PO QA Release standup PM Ops Lead Release Pair
  • 56. st li k c ed up a hn c sae esta teri Relear d ri Puapig o r n de C d includes ep A d nc Qloy A ta ep cc A to Release Retrospectives
  • 57. Monitoring And food!
  • 58. What we set out to do What we did What we learned
  • 59. Specialism
  • 60. Invest in Knowledge Sharing Pair programming Design walkthroughs Mob code reviews Training each other Tech Huddles
  • 61. impacts Development impacts Operations
  • 62. Dev Ops Finding Balance
  • 63. People grew
  • 64. Not all happy
  • 65. Yogurt Australia
  • 66. Dev Ops culture
  • 67. Dev Ops A culture and mindset for collaborating between developers and operations
  • 68. Questions? @patkua
  • 69. Creative Commons Credits • • • • • • • • • • • • Wish - http://www.flickr.com/photos/mattzn/2389865675/sizes/o/ Dog food - http://www.flickr.com/photos/mshades/2132689629/sizes/l/ Lottery - http://www.flickr.com/photos/aresauburnphotos/2678453389/sizes/o/ Conversation - http://www.flickr.com/photos/28481088@N00/2417169797/sizes/o/ Happy lego person - http://www.flickr.com/photos/spielbrick/5360816224/sizes/o/ Sad lego person - http://www.flickr.com/photos/kalexanderson/5421517469/sizes/o/ Brain - http://www.flickr.com/photos/jepoirrier/954701212/sizes/o/ Yogurt - http://www.flickr.com/photos/geishabot/4579250516/sizes/o/ Kookaburra - http://www.flickr.com/photos/lythari/4112022704/sizes/o/ Echidna - http://www.flickr.com/photos/quollism/8470348736/sizes/o/ Wombat - http://www.flickr.com/photos/83028655@N08/7695706186/sizes/o/ Koala - http://www.flickr.com/photos/albertofarzas/7007546026/sizes/o/

×