The Seven DevOps Sins
- 7. The DevOps Sin of Lust
- 8. Shiny!
- 10. The DevOps Sin of Gluttony
- 11. DevOps All the Things!
- 12. How To Eat an Elephant?
- 16. Automate
- 17. The DevOps Sin of Greed
- 18. Cost of Delay From: Lean Enterprise
- 19. Mind Map
- 20. The DevOps Sin of Sloth
- 21. Idle Time
- 23. Google
- 24. Lean Enterprise
- 25. The DevOps Sin of Wrath
- 26. Interruptions
- 27. Kanban
- 28. WIP Limits “Part of the purpose of WIP limits is to reveal opportunities for improvement. Imposing WIP limits will focus attention on work which is blocked or hard to complete, since our inability to complete it prevents us picking up new work. At this point it’s tempting to relax WIP limits to make sure ‘something is getting done’” “It’s essential to avoid this temptation and address the sources of the problem instead.” – LEAN ENTERPRISE
- 31. Stop
- 32. Tyranny of the Immediate
- 33. Why Isn’t This Done Yet?
- 34. The DevOps Sin of Envy
- 35. Eisenhower Matrix Urgent Not Urgent Important Do this work: • Finish a time sensitive project • Complete benefits enrollment • Provide info to unblock other teams Schedule this work: • Next quarter planning • Sprint/scrum activities • Training Not Important Delegate this work: • Automatable tasks • Research new services for teams to use • Ticket queue eval, prioritization Delete this work: • Checking Twitter
- 36. X Does it, Why Can’t We? https://fontmeme.com/netflix-font/
- 37. The DevOps Sin of Pride
- 38. DevOps
- 40. Why Must I Explain It?
- 41. Westrum Cultures
- 42. Pathological
- 43. Bureaucratic
- 44. Generative
- 45. Now What?
- 46. Learn
- 48. Accelerate
- 49. Experiment
- 50. Adapt
- 51. Care and Act
- 52. Success!
- 53. Tolstoy! “Everyone thinks of changing the world, but no one thinks of changing themselves.” - Leo Tolstoy