DevOps is the new Agile. Everyone “does it” but few fully embrace it. This talk will focus on common pitfalls and how to ensure your entire team — ops, IT, sysadmins, SREs and developers — stop blaming each other and work together.

1. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Emily Freeman // @edi0ngemily
Humpty Dumpty
A Story of DevOps
Gone Wrong

2. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Emily Freeman
Developer Advocate @ Kickbox
@edi=ngemily
Emily Freeman // @edi0ngemily

3. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Humpty Dumpty sat on a wall,
Humpty Dumpty had a great fall.
All the king’s horses and all the king’s men
Couldn’t put Humpty together again.
Humpty Dumpty
Emily Freeman // @edi0ngemily

4. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Humpty Dumpty sat on a wall,
Humpty Dumpty had a great fall.
All the king’s horses and all the king’s men
Couldn’t put Humpty together again.
Humpty Dumpty
Emily Freeman // @edi0ngemily

5. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
You see, Humpty
is a deploy.
Emily Freeman // @edi0ngemily

6. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
You see, Humpty
is a deploy.
Emily Freeman // @edi0ngemily

7. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Humpty Dumpty sat on a wall,
Humpty Dumpty had a great fall.
All the king’s horses and all the king’s men
Couldn’t put Humpty together again.
The Important Bit
(In case you missed it.)
Emily Freeman // @edi0ngemily

8. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
(It’s ops.)
Emily Freeman // @edi0ngemily

9. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
But it doesn’t have to
be that way.
Emily Freeman // @edi0ngemily

10. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
But it doesn’t have to
be that way.
Emily Freeman // @edi0ngemily

11. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Change is hard.
And a liGle scary.
Emily Freeman // @edi0ngemily

12. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Change is hard.
And a liGle scary.
Emily Freeman // @edi0ngemily

13. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
History
We start by looking back.
Emily Freeman // @edi0ngemily

14. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
History
We start by looking back.
Emily Freeman // @edi0ngemily

15. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
History
We start by looking back.
Emily Freeman // @edi0ngemily

16. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Conflict
We have different priori0es.
Emily Freeman // @edi0ngemily

17. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Conflict
We have different priori0es.
Emily Freeman // @edi0ngemily

18. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Emily Freeman // @edi0ngemily

19. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Fundamentally unfair.
Emily Freeman // @edi0ngemily

20. HUMPTY DUMPTY | A Story Of DevOps Gone Wrong
And they deserve
to feel like this.
Emily Freeman // @edi0ngemily

21. OPERATIONS | Empower Your Developers
OperaIons
Empower Your Devs
Emily Freeman // @edi0ngemily

22. OPERATIONS | Empower Your Developers
Trust Your Team
Emily Freeman // @edi0ngemily

23. OPERATIONS | Empower Your Developers
Bridge the
Skills Gap
Emily Freeman // @edi0ngemily

24. OPERATIONS | Empower Your Developers
Bridge the
Skills Gap
Emily Freeman // @edi0ngemily

25. OPERATIONS | Empower Your Developers
Read-Only Logs
Emily Freeman // @edi0ngemily

26. OPERATIONS | Empower Your Developers
Read-Only Logs
Emily Freeman // @edi0ngemily

27. OPERATIONS | Empower Your Developers
Consistency
Emily Freeman // @edi0ngemily

28. OPERATIONS | Empower Your Developers
Source Control
Sharing is caring.
Emily Freeman // @edi0ngemily

29. OPERATIONS | Empower Your Developers
On-Call RotaIon
Wake me up. I dare you.
Emily Freeman // @edi0ngemily

30. OPERATIONS | Empower Your Developers
On-Call RotaIon
Wake me up. I dare you.
Emily Freeman // @edi0ngemily

31. OPERATIONS | Empower Your Developers
Simple Deploys
Emily Freeman // @edi0ngemily

32. OPERATIONS | Empower Your Developers
Simple Deploys
Emily Freeman // @edi0ngemily

33. DEVELOPERS | Don’t Be Assholes
Developers
Don’t Be Assholes
Emily Freeman // @edi0ngemily

34. DEVELOPERS | Don’t Be Assholes
Plan Together
Emily Freeman // @edi0ngemily

35. DEVELOPERS | Don’t Be Assholes
Plan Together
Emily Freeman // @edi0ngemily

36. DEVELOPERS | Don’t Be Assholes
Small Changes
Emily Freeman // @edi0ngemily

37. DEVELOPERS | Don’t Be Assholes
Small Changes
Emily Freeman // @edi0ngemily

38. DEVELOPERS | Don’t Be Assholes
Communicate
Emily Freeman // @edi0ngemily

39. DEVELOPERS | Don’t Be Assholes
Yes, And…
Emily Freeman // @edi0ngemily

40. DEVELOPERS | Don’t Be Assholes
Stay Open
Emily Freeman // @edi0ngemily

41. DEVELOPERS | Don’t Be Assholes
Stay Open
Emily Freeman // @edi0ngemily

42. DEVELOPERS | Don’t Be Assholes
Be Humble
Emily Freeman // @edi0ngemily

43. DEVELOPERS | Don’t Be Assholes
Be Humble
Emily Freeman // @edi0ngemily

44. FAILURE | Prac=ce Failing Together
Embrace Failure
It happens. Seriously.
Emily Freeman // @edi0ngemily

45. FAILURE | Prac=ce Failing Together
Embrace Failure
It happens. Seriously.
Emily Freeman // @edi0ngemily

46. FAILURE | Prac=ce Failing Together
Leave Your Ego
At The Door
Emily Freeman // @edi0ngemily

47. FAILURE | Prac=ce Failing Together
Leave Your Ego
At The Door
Emily Freeman // @edi0ngemily

48. FAILURE | Prac=ce Failing Together
Don’t Point
Fingers
Make failure fabulous.
Emily Freeman // @edi0ngemily

49. FAILURE | Prac=ce Failing Together
Don’t Point
Fingers
Make failure fabulous.
Emily Freeman // @edi0ngemily

50. FAILURE | Prac=ce Failing Together
Post-Incident
Reviews
They’re not op0onal.
Emily Freeman // @edi0ngemily

51. Here’s som example text
1. What happened?
2. What was impacted?
3. When did it happen?
4. Who was involved?
5. How was it discovered?
6. Why did it happen?
7. What’s the solu0on?
8. When will it be fixed?
Post-Incident
Reviews
FAILURE | Prac=ce Failing Together
Emily Freeman // @edi0ngemily

52. Here’s som example text
1. What happened?
2. What was impacted?
3. When did it happen?
4. Who was involved?
5. How was it discovered?
6. Why did it happen?
7. What’s the solu0on?
8. When will it be fixed?
Post-Incident
Reviews
FAILURE | Prac=ce Failing Together
Emily Freeman // @edi0ngemily

53. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Making your job
awesome is your job.
Emily Freeman // @edi0ngemily

54. Here’s som example textHUMPTY DUMPTY | A Story Of DevOps Gone Wrong
Emily Freeman
Developer Advocate @ Kickbox
@edi=ngemily
Emily Freeman // @edi0ngemily