easy one!

more automation==less errors,

reproducible workloads

your favorite scripting language,

can be declarative too!

WHY

HOW

customer value first, delivering value to user, building solutions, not only apps

pipelines please, with quality gateways

WHY

HOW

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

WHY

HOW

embrace failure, discuss fragility, never hide anything under the carpet

blameless post-mortems

WHY

HOW

add confidence in pushing value to production, remove FUD

ASAP without hesitation,

see something?

DO something

WHY

HOW

best way to learn?

15% failure (scientific study)

try and document your findings, aim for the "root cause", inject failure (cf. symian army)

WHY

HOW

the Backlog is

your living pet,

it must stay

up-to-date and healthy

planned meetings with stakeholders to align business with work

WHY

HOW

taking shortcuts w/ delivery can make you faster at fixing things

have a hacking budget, keep quality, never indulge in cowboy mode

WHY

HOW

iterations are the agile practice of devops

many frameworks, lots of option, pick yours

WHY

HOW

less organization silos

more shared vision
1+1=3

get c-level support to push various roles into partners

WHY

HOW

Efficient devops teams involve self-assessment of people and skills. Purpose driven people have better business value.

Pass tests, try another role, see if it fits you better

WHY

HOW

if you stop learning, you actually go backwards

take 1h/day to do non-commissioned work

WHY

HOW

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)

WHY

HOW

no more top bottom design, negotiation over dummy execution

introduce agility by delivering value and then suggesting change (see MEASURE)

WHY

HOW

you build it

you run it,

and then only

you will master it

get to really know

your env. configs,

release process,

capacity, etc.

WHY

HOW

because important is not urgent. downtime is not bearable!

eye candy

and new features

can wait

fix bugs ASAP,

see

Negotiate+Questions

WHY

HOW

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 official room for it.

people should feel blameless

to ask the 5 W's

WHY

HOW

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

WHY

HOW

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 specific area

(think SRE, TDD devs, SecOps)

WHY

HOW

because the usual suspects: bugs, regressions, rotting software

as early as possible, automated AMAP, (in production too!)

WHY

HOW

we need to USE tools, tech and technics, because we solve problems.

not the other way round /!\

question, try and qualify

(make or buy?)

WHY

HOW

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".

it's like open source,

but inside your org.

WHY

HOW

part of the

devops feedback loop,

you run it==you watch it

architect for observability

develop with tracing

operate with APM

WHY

HOW

team members should be able to tell why this implementation or this design strategy, how it fits bizops

grooming, poker planning, etc.

WHY

HOW

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.

WHY

HOW