Slide 1
Slide 1 text
DOING DEVOPS
FROM A TO ZEN
djalal, coach/trainer
(@enlamp)
Slide 2
Slide 2 text
No content
Slide 3
Slide 3 text
No content
Slide 4
Slide 4 text
one last thing (first)
one last thing (first)
this is NO authorative content
this is NO authorative content
just MY 5-year DevOps practice
just MY 5-year DevOps practice
“YMMV”
“YMMV”
slides have been reviewed by certified
slides have been reviewed by certified
trainer
trainer
no BS, vendor agnostic, buzzword free
no BS, vendor agnostic, buzzword free
Slide 5
Slide 5 text
No content
Slide 6
Slide 6 text
AUTOMATE
easy one! more
automation = less
errors, reproducible
workloads
your favorite scripting
language, can be
declarative too!
Slide 7
Slide 7 text
No content
Slide 8
Slide 8 text
BUILD
customer value rst,
delivering value to user,
building solutions, not
only apps
pipelines please, with
quality gateways
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
COMMIT all the things
to keep every piece of
code, doc, infra, test,
etc. under an auditable
system
git everything. bonus:
take a look at “gitops”
set of principles
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
DISCUSS failures
embrace failure,
discuss fragility, never
hide anything under the
carpet
blameless post-
mortems
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
ELIMINATE fragility
add con dence in
pushing value to
production, remove
FUD
ASAP without
hesitation, see
something, DO
something
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
FAIL and learn
best way to learn? at
least 15% failure rate
scienti c study
try and document your
ndings, aim for the
“root cause”, inject
failure (cf. symian
army)
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
GROOMING
the backlog is your
living pet, it must stay
up-to-date and healthy
planned meetings with
stakeholders to align
business with work
Slide 19
Slide 19 text
No content
Slide 20
Slide 20 text
HACK
taking shortcuts w/
delivery can make you
faster at xing things
have a hacking budget,
keep quality, never
indulge in cowboy
mode
Slide 21
Slide 21 text
No content
Slide 22
Slide 22 text
ITERATE
iterations are the agile
practice of devops
many frameworks, lots
of option, pick yours
Slide 23
Slide 23 text
No content
Slide 24
Slide 24 text
JOIN forces
less organization silos
1+1=3
more shared vision
get c-level support to
push various roles into
partners
Slide 25
Slide 25 text
No content
Slide 26
Slide 26 text
KNOW yourself
E cient devops teams
involve self-assessment
of people and skills.
Purpose driven people
have better business
value.
Pass tests, try another
role, see if it ts you
better
Slide 27
Slide 27 text
No content
Slide 28
Slide 28 text
LEARN
if you stop learning, you
actually go backwards
take 1h/day to do non-
commissioned work
Slide 29
Slide 29 text
No content
Slide 30
Slide 30 text
MEASURE
no monitoring==no
feedback
can’t take the next step
if you can’t see nothing
set business KPI, don’t
only stare (at
dashboards), share
alerts (or progress)
Slide 31
Slide 31 text
No content
Slide 32
Slide 32 text
NEGOTIATE
no more top bottom
design, negotiation over
dummy execution
introduce agility by
delivering value and
then suggesting change
(see MEASURE)
Slide 33
Slide 33 text
No content
Slide 34
Slide 34 text
OPERATE
you build it, you run it,
and then only you will
master it
get to really know you
env con gs, release
process, capacity, etc.
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
PRIORITIZE
because important is
not urgent. downtime is
not bearable! eye candy
and new features can
wait
x bugs ASAP
, see
Negotiate+Questions
Slide 37
Slide 37 text
No content
Slide 38
Slide 38 text
QUESTION
tasks/priorities
as team maturity
grows, any member will
challenge tasks and
priorities. that’s a good
sign. no HiPPO (highest
paid person’s opinion)
any more
give special moments,
make o cial room for
it. people should feel
blameless to ask the
W’s
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
RELEASE to production
can’t do devops without
releases, or else it’s just
another local
optimization with silos
ideally use deployment
pipelines, at least stop
manually running
commands on SSH
Slide 41
Slide 41 text
No content
Slide 42
Slide 42 text
SHAPE your skills
transformation needs
people, not the
traditional ones.
specialists are too deep
and narrow (the “I”
shape).
orgs should shop for
“T” shaped people, with
broad knowledge mixed
with some expertise in
a speci c area (think
SRE, TDD devs,
SecOps)
Slide 43
Slide 43 text
No content
Slide 44
Slide 44 text
TEST
because the usual
suspects: bugs,
regressions, rotting
software
as early as possible,
automated AMAP
, (in
production too!)
Slide 45
Slide 45 text
No content
Slide 46
Slide 46 text
USE
we need to USE tools,
tech and technics,
because we solve
problems. not the other
way round /!\
question, try and qualify
(make or buy?)
Slide 47
Slide 47 text
No content
Slide 48
Slide 48 text
VOLUNTEER
help others in your
team, or other teams:
invaluable bonds in the
long term, especially if
not on your payroll
agree on inner source
principles. like open
source, but inside your
org.
Slide 49
Slide 49 text
No content
Slide 50
Slide 50 text
WATCH production
part of the devops
feedback loop, you run
it, you watch it
practice observability,
or APM
Slide 51
Slide 51 text
No content
Slide 52
Slide 52 text
XPLAIN why
team members should
be able to tell why this
implementation or this
design strategy, how it
ts bizops
grooming, poker
planning, etc.
Slide 53
Slide 53 text
No content
Slide 54
Slide 54 text
YIELD progress
progress is one of
major metric in devops
practice. ie. more
progress=more
customer value=more
motivation.
measure it, share,
celebrate, rinse and
repeat. watch for the
technical debt budget.
Slide 55
Slide 55 text
No content
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
BONUS 1: top 10 items showing you are “doing
devops”
1. Written Business objectives
2. Up to date Backlog
3. “* as Code” git Repositories
4. Documentation for any process
5. Delivery pipelines
6. Automated Tests
7. Peer Reviews
8. Software artefacts
9. Measurement dashboards
10. Blameless post-mortems
Slide 58
Slide 58 text
BONUS 2: List of metrics to measure success
Release velocity
Mean Time To Repair
Versions per pipeline stage
Quality and Review Status per Version
Active, recent and planned Deployments & Releases
Environment Availability & Schedule
Slide 59
Slide 59 text
Thanks!
questions & feedback
welcome
catch me