Going Big with DevOps
1
Scaling Sustainable,
Continuous and
Solid success
Slide 2
Slide 2 text
2
Hello world
Meet github.com / kelseyhightower / nocode
Not made up:
• 33.7k stars
• 3k forks
• 2,634 issues
• 394 pull requests
Slide 3
Slide 3 text
3
Hello world
Hey, I’m Xavier Bruhiere
Head of Data Engineering at Lazada eLogistics
4 50 120 8000 pax
Companies I deployed things for
Slide 4
Slide 4 text
4
Hello world
All happy families are alike;
Each unhappy family is
unhappy in its own way
-- Anna Karenina principle
Slide 5
Slide 5 text
5
Introduction
The elephant in the room: what is DevOps?
Slide 6
Slide 6 text
6
Introduction
Instead: why DevOps?
50 years
Slide 7
Slide 7 text
7
Introduction
Instead: what is DevOps success?
> Agility
> Reliability
> Velocity
> Cost
> Confidence
spoiler
Slide 8
Slide 8 text
8
Introduction
Again: what is DevOps success?
> Scalable
> Sustainable
> Impactful
Keep in sight
Slide 9
Slide 9 text
9
1. Cross-team
collaboration
2. Spread enterprise-wide
3. Business impact that
matters
AGENDA
Slide 10
Slide 10 text
01
Cross-team collaboration
10
Slide 11
Slide 11 text
11
Cross-team
Cross-team brain
DevOps Journey
• Customer expectations
• Business goals
• Tech trade-off
• Operational capacity
Dev
Sys
QA
Business
Track releases – Align incentives
Slide 12
Slide 12 text
12
Cross-team
The culture glue
Recipe for success
• Top-down
• Single-team mindset
• Growth mindset
DevOps Journey
not my job
Slide 13
Slide 13 text
13
Cross-team
3 ownership models
Collaboration
Squads Role Platform
End-to-end
Vertical skills
Consultant
Versatile
More capacity
More specific/generic
Slide 14
Slide 14 text
14
Cross-team
Bonus ownership model
Collaboration
The unicorn data scientist
Slide 15
Slide 15 text
15
Cross-team
The product owner
Key Buffer Role
• Translate requirements
• Understand domain
• Filter requests
• Document
Collaboration
Slide 16
Slide 16 text
16
Cross-team
What to share
Tech skills
Tech capacity
Knowledge
Make everyone responsible
Rotate on-call
Company transparency
Help trade-off
Slide 17
Slide 17 text
17
Cross-team
What to share (2)
Business domain
Teams KPI
Knowledge
Empower engineers
Connect people
Legitimate efforts
Foster empathy
Slide 18
Slide 18 text
02
Spread enterprise-wide
18
Slide 19
Slide 19 text
19
Spread
Engineering a good
Strategy
Horizontal scaling: across tech
Vertical scaling: across functions & departments
Slide 20
Slide 20 text
20
Spread
Engineering a good
Strategy (2)
Manage legacy
Identify where it matters
Slide 21
Slide 21 text
21
Spread
Getting started - Tech
Scaling horizontally
Engineers to learn from each-other
• Open the tooling repositories
• Lunch and learn
• Mentorship
• Hackathons
• Experimentation
• All-hands
• …
Slide 22
Slide 22 text
22
Spread
Scaling horizontally
You build it – you ship it – you fix it
Central
tooling
Building
stuff
Slide 23
Slide 23 text
23
Spread
Scaling horizontally & vertically
Opt-in model
Managed
Tech platform
Legacy stuff
That works
Slide 24
Slide 24 text
24
spread
Your deploys should be
as boring, straightforward and
stress-free as possible
-- Zach Holman (How to deploy software)
Slide 25
Slide 25 text
25
Spread
Scaling vertically
Get people involved
Production
Feature Staging
Dev
User
Business
Product Owner
Engineer
Feedback
Slide 26
Slide 26 text
26
Spread
Scaling vertically
Testing in production
Eating your own dog food
v5
v4
10%
90%
Slide 27
Slide 27 text
27
Spread
Risks & Challenges (1)
Optimizing local optimums
Limiting scopes of knowledge
Falling in love with the tech
Infinite feedback loop
Security
Slide 28
Slide 28 text
28
Spread
Risks & Challenges (2)
Machine learning and Big Data
Slide 29
Slide 29 text
03
Business impact that matters
29
Slide 30
Slide 30 text
30
Business impact
Build it
and they will come
-- someone with no customers
Slide 31
Slide 31 text
31
Business impact
1. The right things to fix
McKinsey coined the 2 speeds IT
• Identify high-leverage areas
• Understand legacy
Slide 32
Slide 32 text
32
Business impact
2. Communicate
DevOps is not a side project
Set ambitious expectations
Plan transparently
Educate as you go
Slide 33
Slide 33 text
33
Business impact
3. Measure
For a good impact, take:
Good KPIs
Great feedback loop
Lots of iterations
Slide 34
Slide 34 text
34
Business impact
4. Let them know | Customer Care
# Brag about it
# Replicate success
# Train customers
# On-board new features
# Share knowledge
# Open source
# Improve
# Promote
# Survey
Slide 35
Slide 35 text
35
Culture
Sharing
Cross-*
Communication
Iteration
Results
Wrapping Up