There has been a lot of misunderstandings around the topic of DevOps. This presentation makes it clear it is more of interaction between teams to deliver quality software to the stakeholders in a timely rather than focusing on tools.

1. DEVOPS
Adetunji Sunmonu
D e f i n i t i o n o f D o n e

2. When is your software project
done?
2

3. You are not paid for your code
to run on machine, but in
production
3
Tunji Sunmonu

4. 4

5. THEMES
5

6. C–CULTURE
A–AUTOMATION
M–MEASUREMENT
S-SHARING
6

7. CULTURE
7

8. Lowering the risk of change
(from all aspects of delivery)
8

9. “Synergy” between different
functions of business.
9

10. Keep the organization
competitive not just keep the
light on
10

11. There is no one right way
11

12. Scrum Master == DevOps Engineer?
Retros == Logstash?
12

13. AUTOMATION
13

14. “Automation allows more time
for Design”
“Repeatable Results, Faster”
14

15. Automated Testing
15

16. Infrastructure as code
16

17. One Source of Truth
17

18. Consistency - which enables
sharing and caring
18

19. (Continuous) Deployment
19

20. MEASUREMENT
20

21. Monitoring
21

22. Measure everything
22

23. Learn from your Infrastructure.
Anticipate
23

24. Extract business value
24

25. Metrics for learning and
feedback.
25

26. SHARING
26

27. Shared Goal – improve reliability
and speed
27

28. Shared Problem Space –
deployment, delivery
28

29. Shared Priorities – what gets
improved first
29

30. Shared Location – minimize communication
effort, make it personal
30

31. Shared Communication – chat,
wiki, mailing list
31

32. Shared Codebase – code and
infra code
32

33. Shared Responsibility – fix the
build, fix the deploy
33

34. Shared Workflow – one button
deply
34

35. Shared Knowledge
35

36. Shared Success and Failure –
common experience, history
36

37. ANTI-PATTERN
37

38. 38

39. 39

40. 40

41. 41

42. 42

43. 43

44. 44

45. 45

46. The software isn’t finished until
the last user is dead
46
Sidney Markowitz

47. References
Patrick Debois - Devops with the S for sharing
Matthew Skelton - What Team Structure is
Right for DevOps to Flourish?
47