Tweet
Tweet

Slide 1

Slide 1 text

Community: The Secret Ingredient for DevOps Nathen Harvey | VP, Community Development | @nathenharvey

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

Community

Slide 4

Slide 4 text

What is DevOps?

Slide 5

Slide 5 text

DevOps – The Beginning

Slide 6

Slide 6 text

No content

Slide 7

Slide 7 text

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?!

Slide 8

Slide 8 text

http://www.flickr.com/photos/docsearls/5500714140 Operations QA Dev Product Management

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

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

Slide 11

Slide 11 text

DevOps?!

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

DevOps is reinventing how we run our businesses

Slide 14

Slide 14 text

DEVOPS A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.

Slide 15

Slide 15 text

People First People Products Companies

Slide 16

Slide 16 text

Eliminate Waste Constantly evaluate processes What am I doing that I don’t need to do?

Slide 17

Slide 17 text

Pull over Push Capacity and customer need drives the work. Visualize the work. Eliminate bottlenecks Provide context Align process and resources with market demand

Slide 18

Slide 18 text

Continuous Improvement Constantly evaluate processes Improve operational efficiency What one thing could be done differently to drive a better outcome?

Slide 19

Slide 19 text

Radical Change Operational efficiency may not be enough Buy-in from across the organization What is required to disrupt our business?

Slide 20

Slide 20 text

Small Batches & Experimentation Compress feedback cycles Always Be Learning What is the minimum viable product?

Slide 21

Slide 21 text

Embrace Failure Failure is guaranteed Failure is not an abnormal event Failure is an opportunity to learn

Slide 22

Slide 22 text

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

Slide 23

Slide 23 text

DIVERSITY

Slide 24

Slide 24 text

A quick aside…

Slide 25

Slide 25 text

Principles in Practice

Slide 26

Slide 26 text

Empowered Teams •  Permission to act •  Paired with the context to make good decisions •  With leaders who care about your purpose •  And share your beliefs

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

@nathenharvey Demo Days!

Slide 29

Slide 29 text

@nathenharvey Demo Days! •  Weekly •  Anyone with anything to show •  Invite everyone •  Record it and post it internally

Slide 30

Slide 30 text

Chef Demo Days Playlist https://goo.gl/UEfyKl

Slide 31

Slide 31 text

@nathenharvey

Slide 32

Slide 32 text

@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

Slide 33

Slide 33 text

@nathenharvey Post Mortems •  Time to Detect •  Time to Resolve

Slide 34

Slide 34 text

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

Slide 35

Slide 35 text

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

Slide 36

Slide 36 text

Non-bullet slide Non-bullet slide subtitle Local Community

Slide 37

Slide 37 text

http://dctechslack.com

Slide 38

Slide 38 text

No content

Slide 39

Slide 39 text

DEVOPS A cultural and professional movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners.

Slide 40

Slide 40 text

WHO PRACTICES DEVOPS? EVERYONE •  We are not generalists – we are well connected specialists •  We are all DevOps

Slide 41

Slide 41 text

No content

Slide 42

Slide 42 text

Your are responsible… For your learning For your development For your career For your teammates For lots of important things

Slide 43

Slide 43 text

…but you are not alone Find a mentor Lean on your peers Mentor someone Give back

Slide 44

Slide 44 text

DevOps Transformation Nathen Harvey | VP, Community Development | @nathenharvey