During this talk we're going to talk about DevOps from cultural perspective and why is it very important from company perspective to focus more on cultural development rather than on thinking about DevOps as one another reason to deploy the cutting-edge technologies stack.

1. We're all DevOps
Mikhail Chinkov

2. STAGE
4
STAGE
2
STAGE
1
STAGE
3
2017
Driving DevOps in
tech-companies
2014
Working in Web
2016
Thinking about
DevOps
2018
Driving DevOps within
Berlin area
About me

3. Overview
1
2
3
Terminology
Reality
Future

4. TERMINOLOGY
Why DevOps is not an engineer?

5. Engineer and DevOps
1
2
3
I'm not a DevOps Engineer
I'm rather a Platform Engineer (although DevOps-driven)
There is no DevOps Engineer in this hall
The title "DevOps Engineer" sounds like an industry's diarrhea4

6. “DevOps is the way of building
software for technology
companies

7. Lean
emphasize the value
stream to end-users
Culture
focus on people and
collaboration
Automation
delegating the
routine to computers
Measurement
emphasize the feedback
from metrics
DevOps as evangelists see it
Sharing
sharing of knowledge
and experiences

8. Lean
emphasize the value
stream to end-users
Culture
focus on people and
collaboration
Automation
delegating the
routine to computers
Measurement
emphasize the feedback
from metrics
DevOps as companies see it
Sharing
sharing of knowledge
and experiences

9. Problem domains
Bloody
Enterprise
Messy
Startup
Organization is moving very slow, difficulties of
changing the mindset of thousands employees
People don't know how to become DevOps, problems
with the resources allocation

10. Why are we not DevOps yet?
REALITY

11. Data-Driven as analogy

12. DevOps Report by Puppet Labs
So-so
Medium
performers
Perfect
Elite
performers
Good
High
performers
Deployment frequency
Lead time for changes
Time to restore app
Bad
Low
performers
Change failure rate

13. The problem of standards
1
2
3
Focused on "outputs", not on "outcomes"
"Outcomes" are unstandardised per se
The company itself should define its DevOps state and roadmap
The company doesn't understand it
It gets much harder to prioritise DevOps cultural movement
4
5

14. Before "DevOps"

15. Getting shit done
1
2
3
Infra code is rewritten
Human monitoring is implemented
Bulletproof CI/CD core is designed
Clear-cut Staging/QA environments are placed
Everything is on top of Docker and Kubernetes ofc
4
5

16. After "DevOps"

17. What's wrong?
1
2
3
There is still the huge time pressure on Platform Engineers
Technologies are scalable, humans aren't
Demovitation of knowledge sharing
Collaboration problems (burnout/apathy)4

18. How can we become DevOps?
FUTURE

19. The lifecycle
STAGE
4
STAGE
2
STAGE
1
STAGE
3
Knowledge
Engineers run and maintain
apps in prod themselves
Blackbox
Nobody knows what's
inside the infra
Awareness
Infra is clear and visible
for all engineers
Contribution
Engineers contribute to
the infra core on demand

20. The ideal setup

21. Empathy
Striving to faster
response time
Coaching
Workshops, pair
programming
Confidence
Self-confidence of
engineers as a goal
Platform Team
Documentation
Cover absolutely all
platform aspects
Balance
Iterating between tech,
processes, culture
Product Team
Self-sufficiency,
roadmap, stakeholders
Checklists
Process as a routine
repeatable operation
Снаружи Внутри

22. “After reaching all technical and cultural
capabilities, the company's DevOps
transformation will be based on the
feedback from both business and
platform metrics

23. Questions?
Contact Blog