Community, the secret ingredient for DevOps

This is an exploration of the community-side of DevOps. How do you participate in the larger DevOps community? How do you build an "internal" community around DevOps practices? Open source?! how do I even start with contributing to the community?

Hear about some successful teams are incorporating lessons learned from open source, DevOps, and other communities. Leave with some ideas of things to try in your own environment.

From DevOpsDays Austin 2016.

Transcript

1. Community, the secret ingredient for DevOps Nathen Harvey @nathenharvey
2. Nathen Harvey VP, Community Development at Chef Co-host of the Food Fight Show Podcast Occasional farmer – http://ei.chef.io Love eggs – http://eggs.chef.io Part-time detective - http://bit.ly/detectivedecker @nathenharvey nharvey@chef.io
3. RailsConf 2010 “A hashtag does not a movement make.”
4. RailsConf 2010
6. Community •  Highly distributed •  Leverage social tools •  Leverage events for ideation •  Open to everyone
8. Jumpstart Kit Repeatable Demo Ease adoption by making it easier to get started SHARE Community of Practice Knowledge Share Internal Meetup Make it easy to show the value to engineers & leadership Create a place to share learnings: wiki, forum, email list Setup open meetings to talk about Chef, automation, life Transform One Team Make Time for Mentoring Get one solid success before moving on COACH Mentorship vs. Ownership Give Up Control Champions Group Dedicate time to help others solve problems Let others fail before teaching them how to succeed Meet regularly with “champions” from different groups DevOps Day Sponsor Local Meetups/Events Plan a 1-day event to showcase demos, talks NURTURE Maintaining Momentum Internal Training Program Gather Regular Feedback The local community can be a great recruiting source Create an internal training program to speed education Survey Chef users to see where pain points might be Forming Communities
9. Jumpstart Kit •  Ease adoption by making it easier to get started •  Time from hire to first production deploy
10. Demo Days!
11. Demo Days! •  Weekly
12. Demo Days! •  Weekly •  Anyone with anything to show
13. Demo Days! •  Weekly •  Anyone with anything to show •  Invite everyone
14. Demo Days! •  Weekly •  Anyone with anything to show •  Invite everyone •  Record it and post it internally
15. Lunch & Learn
16. FORM DIVERSE BONDS
17. FORM DIVERSE BONDS •  Take people to lunch, or have meetings, with people outside your specialty
18. FORM DIVERSE BONDS •  Take people to lunch, or have meetings, with people outside your specialty •  Ask them what they do, and try and understand their problems and perspective
19. FORM DIVERSE BONDS •  Take people to lunch, or have meetings, with people outside your specialty •  Ask them what they do, and try and understand their problems and perspective •  Legal, Finance, Sales, Marketing, Business Development, Software Development, Systems Administrators, Security Professionals, Product
21. Knowledge Share
22. Listen Up!
23. Jumpstart Kit Repeatable Demo Ease adoption by making it easier to get started SHARE Community of Practice Knowledge Share Internal Meetup Make it easy to show the value to engineers & leadership Create a place to share learnings: wiki, forum, email list Setup open meetings to talk about Chef, automation, life Transform One Team Make Time for Mentoring Get one solid success before moving on COACH Mentorship vs. Ownership Give Up Control Champions Group Dedicate time to help others solve problems Let others fail before teaching them how to succeed Meet regularly with “champions” from different groups DevOps Day Sponsor Local Meetups/Events Plan a 1-day event to showcase demos, talks NURTURE Maintaining Momentum Internal Training Program Gather Regular Feedback The local community can be a great recruiting source Create an internal training program to speed education Survey Chef users to see where pain points might be Forming Communities
24. One Team
27. Coaching Kata 1.  What is the target condition? 2.  What is the actual condition? 3.  What are the obstacles? 4.  What is the next step? 5.  When can we see what we’ve learned from that next step? http://www.lean.org/kata/Archive.cfm?KataItemId=3
28. Jumpstart Kit Repeatable Demo Ease adoption by making it easier to get started SHARE Community of Practice Knowledge Share Internal Meetup Make it easy to show the value to engineers & leadership Create a place to share learnings: wiki, forum, email list Setup open meetings to talk about Chef, automation, life Transform One Team Make Time for Mentoring Get one solid success before moving on COACH Mentorship vs. Ownership Give Up Control Champions Group Dedicate time to help others solve problems Let others fail before teaching them how to succeed Meet regularly with “champions” from different groups DevOps Day Sponsor Local Meetups/Events Plan a 1-day event to showcase demos, talks NURTURE Maintaining Momentum Internal Training Program Gather Regular Feedback The local community can be a great recruiting source Create an internal training program to speed education Survey Chef users to see where pain points might be Forming Communities
29. Meetups •  Listen •  Learn •  Present •  Interact
31. Host Meetups
33. Bring the conference to your team •  Internal Events •  Automation Symposium •  Cloud Symposium •  DevOps Symposium •  Introduce new meeting formats •  Open Spaces •  Lean Coffee
35. Road trip!
36. Engineer Exchange
37. Jumpstart Kit Repeatable Demo Ease adoption by making it easier to get started SHARE Community of Practice Knowledge Share Internal Meetup Make it easy to show the value to engineers & leadership Create a place to share learnings: wiki, forum, email list Setup open meetings to talk about Chef, automation, life Transform One Team Make Time for Mentoring Get one solid success before moving on COACH Mentorship vs. Ownership Give Up Control Champions Group Dedicate time to help others solve problems Let others fail before teaching them how to succeed Meet regularly with “champions” from different groups DevOps Day Sponsor Local Meetups/Events Plan a 1-day event to showcase demos, talks NURTURE Maintaining Momentum Internal Training Program Gather Regular Feedback The local community can be a great recruiting source Create an internal training program to speed education Survey Chef users to see where pain points might be Forming Communities
38. You are responsible… •  For your learning •  For your development •  For your career •  For your teammates •  For lots of important things
39. …but you are not alone! •  Find a mentor •  Lean on your peers •  Mentor someone •  Give back
40. Get involved! •  Be active in the community •  Step out of the echo chamber •  Step out of your comfort zone •  Don’t fight stupid, make more awesome! •  Jesse Robbins
43. Nathen Harvey VP, Community Development at Chef Co-host of the Food Fight Show Podcast Occasional farmer – http://ei.chef.io Love eggs – http://eggs.chef.io Part-time detective - http://bit.ly/detectivedecker @nathenharvey nharvey@chef.io