GOING BIG AND F*#&#*G UP

A Cautionary Tale@mikebaukes

1

A History of Success

A New Market in 9 months 

MarketWide Disruption

THE BUSINESS

DevOps

Approved

2

THE PROJECTFunding a DevOps initiative using "risk”

What do we have?

Is it representative of production?

Are we at risk?Risk

/Security

love DevOps

3

COMPANY CULTURE

Teams Spread across Geographies and Organization Charts

Average Request fulfillment was around 2 weeks

Rife with process debt

4

TEAM CULTURE

We recruited the best

Immediately Caused Tension

Elitism & Arrogance began to grow

5

THE PROCESSES

Project Managers = Test Results/Environment Documentation

ITIL = DSL/DML/CMDB & STSDLC = VC Inf/Repeatable Env

Risk = MS/DE Sign-offs

Automation using Chef

Architecture = TRM/Enterprise Continuum

6

TECHNICAL DEBT

90% on Writing Code, 10% on education

10 Environments, Multiple Stage Gates (2 weeks)

Split in 2 groups (newbies/old-school)

Knowledge Vacuum

7

PROGRESSION/REGRESSION

8

LESSONS

1. Empathy

2. Get the Data!

3. DevOps is an HCM issue WTF?

4. In production and not in dev means #fail

9

THANKS@mikebaukes

@scriptrock

@devops

10