DevOps has been around for a decade. In this time it grew from a vague buzzword to a key-subject discussed in and used by several companies. DevOps is more than a group therapy for frustrated IT engineers with new fancy tools! It has impact on most of our workflows – and more! A cultural refactoring complementing bigger projects with even bigger technical or organisational problems aka challenges. What are the show-stoppers when introducing DevOps methods? What are the technical symptoms? Which problems aren’t actually technical? How to approach these issues? This talk won’t give you an introduction to DevOps. It rather highlights where the usage of DevOps methods creates more problems than it solves. We identify potential causes and discuss possible approaches.

1. DevOps
is neither the Answer,
nor the Question!
Arnold Bechtoldt
(inovex)
arbe.io
@arnisoph

2. ?
2

3. My day as a
“DevOpsOp”

4. 4
GitOps in the morning

5. 5
BikeOps

6. 6
ChatOps ...

7. 7
DevOooops ...

8. 8
0800-DevSecNetGoogleOps!

9. 9
OpsDev ...

10. 10
BizDevOps ...

11. 11
BeerOps.…..?!

12. 12
Bullshit Bingo?!

13. But then what is
DevOps about?

14. 14

15. The DevOps Cycle (DevOps Handbook)
15
often fails
here
and here
and here
and here
and here
and here
and here

16. DevOps
is not the answer!
It’s just a buzzword!
16

17. DevOps is ...
… get shit done fast and
quickly deliver it to the customer.
17

18. … and in other words ...
… changing a lot for developers,
sysadmins, technical (dev) leads, QAs,
DBAs and more classical roles!
18

19. … that often leads to ...
… nothing about fun.
19

20. Why is it so hard ...
… in the real world?

21. 21
Automation
Still a thing in 2018 2019!

22. 22
Complexity
Some love their job just too much!

23. 23
Technical Debts
That nobody wants to clean up.

24. 24
Communication
We should meet to not meet again!

25. 25
Politics Everywhere
And Silo-Thinking.

26. DevOpsis not the question! DevOps is normal!
26

27. DevOps is
about culture!
So, culture is key!
27

28. Okay, but how?

29. 29
Autonomous
product-centric teams.

30. 30
Same privileges and tools
for everybody.

31. 31
Replace
human interfaces with
automation (APIs).

32. 32
Standardized platforms
as technical base layer.

33. 33
Expect failures:
Fail Fast. Fail Often.

34. “ If you want to increase your
success rate,
double your failure rate.
34
Thomas J. Watson

35. DevOpsis neither the answer, nor the question!
35

36. 36
inovex.de/jobs

37. Thanks!
37
@arnisoph
inovex.de/jobs

38. Credits
◂ Presentation template by SlidesCarnival
◂ Picture Sources:
◂ pexels.com
◂ pixabay.com
◂ Flickr
◂ Private Source
38