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

DevOps & Community

Nathen Harvey
February 22, 2017

DevOps & Community

Presentation given at NOVA DevOps Meetup.

https://www.meetup.com/NOVA-DevOps/events/236672976/

Nathen Harvey

February 22, 2017
Tweet

More Decks by Nathen Harvey

Other Decks in Technology

Transcript

  1. Community: The Secret Ingredient for DevOps Nathen Harvey | VP,

    Community Development | @nathenharvey
  2. Nathen Harvey VP, Community Development at Chef Co-host of the

    Food Fight Show Podcast Co-organizer of DevOpsDC Meetup Co-organizer of DevOpsDays DC & Baltimore Occasional farmer – http://ei.chef.io Love eggs – http://eggs.chef.io #hugops – http://hugops.chef.io @nathenharvey
  3. Community

  4. What is DevOps?

  5. DevOps – The Beginning

  6. None
  7. Are costs inline with budget? Is the data safe? How

    are you handling data backups? What happens when the cloud has an outage? Will you even realize there's been a outage? What are you using for data persistence?!
  8. http://www.flickr.com/photos/docsearls/5500714140 Operations QA Dev Product Management

  9. http://www.flickr.com/photos/docsearls/5500714140 QA Dev Product Management $ sudo su - Operations

  10. http://www.flickr.com/photos/docsearls/5500714140 http://www.flickr.com/photos/bontempscharly/8094344618 QA Dev Product Management $ sudo su -

    Operations
  11. DevOps?!

  12. None
  13. DevOps is reinventing how we run our businesses

  14. DEVOPS A cultural and professional movement, focused on how we

    build and operate high velocity organizations, born from the experiences of its practitioners.
  15. People First People Products Companies

  16. Eliminate Waste Constantly evaluate processes What am I doing that

    I don’t need to do?
  17. Pull over Push Capacity and customer need drives the work.

    Visualize the work. Eliminate bottlenecks Provide context Align process and resources with market demand
  18. Continuous Improvement Constantly evaluate processes Improve operational efficiency What one

    thing could be done differently to drive a better outcome?
  19. Radical Change Operational efficiency may not be enough Buy-in from

    across the organization What is required to disrupt our business?
  20. Small Batches & Experimentation Compress feedback cycles Always Be Learning

    What is the minimum viable product?
  21. Embrace Failure Failure is guaranteed Failure is not an abnormal

    event Failure is an opportunity to learn
  22. Automation Infrastructure as code is versionable, testable, and repeatable. Strangle

    out manual processes Automation is the foundation of your transformation. No high velocity company has gotten there without automation as a foundation
  23. DIVERSITY

  24. A quick aside…

  25. Principles in Practice

  26. Empowered Teams •  Permission to act •  Paired with the

    context to make good decisions •  With leaders who care about your purpose •  And share your beliefs
  27. 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
  28. @nathenharvey Demo Days!

  29. @nathenharvey Demo Days! •  Weekly •  Anyone with anything to

    show •  Invite everyone •  Record it and post it internally
  30. Chef Demo Days Playlist https://goo.gl/UEfyKl

  31. @nathenharvey

  32. @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
  33. @nathenharvey Post Mortems •  Time to Detect •  Time to

    Resolve
  34. 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
  35. 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
  36. Non-bullet slide Non-bullet slide subtitle Local Community

  37. http://dctechslack.com

  38. None
  39. DEVOPS A cultural and professional movement, focused on how we

    build and operate high velocity organizations, born from the experiences of its practitioners.
  40. WHO PRACTICES DEVOPS? EVERYONE •  We are not generalists –

    we are well connected specialists •  We are all DevOps
  41. None
  42. Your are responsible… For your learning For your development For

    your career For your teammates For lots of important things
  43. …but you are not alone Find a mentor Lean on

    your peers Mentor someone Give back
  44. DevOps Transformation Nathen Harvey | VP, Community Development | @nathenharvey