DevOps

Adoption through Culture, Automation, Measurement, and Sharing

ADAPT February 2014



Sam Brown | @SamuelBrownIV | Blackboard Senior Manager, Engineering Services

Matt Makai | @mattmakai | makaimc on GitHub | Twilio Developer Evangelist

A simpler time...

US Home Prices

My first sys admin

#!/bin/bash

Life was good?

  • Weeks to iron out environment
  • Months to fix unplanned bugs
  • 2 years to deliver value
  • Business users didn't need app

Today

  • What is DevOps?
  • CAMS
  • Specific actions
  • Groups & resources

This is Agile

Is this Agile success?

Competing Interests

Developers -> Business value

Operations -> Stability and security

Aligning Goals

What is DevOps?

DevOps is a collaborative movement started by frustrated DEVelopers and OPerations staff

DevOps Emphasizes

Collaboration

Communication

Integration

Goal

Highly effective team

What DevOps is not

[X] a new tool

[X] a new team

[X] something you can create overnight

Culture

Automation

Measurement

Sharing

CAMS

Specific Actions

Measurement

Anonymous Surveys

  • Open-minded leadership
  • 5-7 minutes, regularly repeated
  • What doesn't make sense?
  • What needs to change?
  • Worst parts of going to production

Retrospectives

  • Listen
  • Blameless
  • What worked?
  • What didn't?
  • What are we changing?

Metrics

  • Time from feature requested to available in production
  • Time from issue reported to fixed in production
  • How quickly can you measure new metrics in production?

Create metrics visibility app

Automation

Move from this...

...to this

Infrastructure as Code

Sharing

External speakers (not salespeople)

Groups

DC Continuous Delivery

DC Configuration Management

DevOps DC

Sharing your OWN stories

Culture

Management must move from approver to obstacle destroyer.

This organization's tech team is amazing.

Wrap up

  • Agile productivity -> DevOps
  • What is DevOps?
  • CAMS actions
  • Groups & resources

Resources

Contact Information

Sam Brown

Matt Makai

Picture references