Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Community: The Secret Ingredient for DevOps

Nathen Harvey
November 01, 2016

Community: The Secret Ingredient for DevOps

Successful DevOps requires collaboration. Collaboration improves when you grow from colleagues to a community.

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.

This was presented at DevOpsDays Ohio https://www.devopsdays.org/events/2016-ohio/welcome/

Nathen Harvey

November 01, 2016
Tweet

More Decks by Nathen Harvey

Other Decks in Technology

Transcript

  1. @nathenharvey 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 #hugops – http://hugops.chef.io @nathenharvey [email protected]
  2. @nathenharvey FORM DIVERSE BONDS •  Take people to lunch, or

    have meetings, with people outside your specialty
  3. @nathenharvey 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
  4. @nathenharvey 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
  5. @nathenharvey Demo Days! •  Weekly •  Anyone with anything to

    show •  Invite everyone •  Record it and post it internally
  6. @nathenharvey Post Mortems •  Invoke the space: here to learn,

    not blame •  Describe the incident •  Establish the timeline •  Identify contributing factors •  Describe customer impact •  Describe remediation tasks •  Describe improvement tasks
  7. @nathenharvey Post Mortems – Who Attends? •  Required   Incident

    commander   People actively involved in incident response   Representative from each team likely to receive action items •  Invited   Engineering, Operations, and everything in-between   The entire company
  8. @nathenharvey Post Mortems – Who Attends? •  Required   Incident

    commander   People actively involved in incident response   Representative from each team likely to receive action items •  Invited   Engineering, Operations, and everything in-between   The entire company   The public
  9. DEVOPS A cultural and professional movement, focused on how we

    build and operate high velocity organizations, born from the experiences of its practitioners.
  10. Building a DevOps Community •  Internal •  Form diverse bonds

    •  Demo Days •  Post Mortems •  External •  Online community •  Meetups and Conferences •  Open Source
  11. You are responsible… •  For your learning •  For your

    development •  For your career •  For your teammates •  For lots of important things
  12. …but you are not alone! •  Find a mentor • 

    Lean on your peers •  Mentor someone •  Give back
  13. 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 #hugops – http://hugops.chef.io @nathenharvey [email protected]