Magic, Myth and the DevOps
12 likes4,418 views
The document discusses the role of myths in shaping behaviors and culture within the DevOps community. It highlights various myths related to team dynamics, skills assessments, and organizational structure while advocating for speaking up and promoting diversity and change within organizations. Key strategies for fostering a positive culture include listening, identifying inconsistencies, and encouraging open dialogue.
Magic, Myth and the DevOps
- 1. Magic, Myth and the DevOps Jennifer Davis @sigje DevOpsDays Vancouver 2014 1
- 2. Agenda • What are Myths? • See the Myths • Speaking up 2
- 3. 3
- 4. The Zero's Journey There is no "One". 4
- 5. Devops is a Myth 5
- 7. Myths based in tradition. 7
- 8. Myths explain the world and our significance. 8
- 9. Myths are the oral history passed around to give value to the unknown. 9
- 10. Myths ... 1 part promise 1 part warning. 10
- 11. Myths are stories. With power to cause action. 11
- 12. Myths are magic. Unseen, invoking behavior. Influencing us. 12
- 13. Myths are programs. Allow us to alter our central algorithm. 13
- 14. Insanity is doing the same thing over and over and expecting different results. 14
- 15. Story of your typical team 15
- 16. 16
- 17. 17
- 18. 18
- 19. 19
- 20. 20
- 21. 21
- 22. 22
- 23. Exposing Hidden Myths 23
- 24. Myth: Finding "The One" • rockstar • ninja 24
- 25. Job Req: Site Rebel Engineer (SRE) Talented team of Jedi, we have, gained significant traction that a business model has, and to expand a real need - - quickly! Looking for smart, we are, energetic, to grow our company at a lightening pace hard-working individuals who want a chance. This is a position that is relegated to the shadows not - your contributions -, have dramatic input on the direction the company goes, thoughts and input will. There are a variety of challenges and obstacles that await you and, excited to see how you go about solving them, are we. 25
- 26. • Certified Jedi Master • 4 years lightsaber experience • ability to carry 80 lbs for 1 mile • X-Wing pilot license • 24 hour oncall With force push and mental persuasion - experience. To join and contribute to a team of smart - desire, talented, to create something bigger than themselves hard-working 26
- 27. Myth: Interview as a gauge of skills 27
- 29. Myth: Outdated Engineer 29
- 30. Myth: Productive Loner 30
- 31. Myth: The "right" way. • identify good culture • current team, background, and effective 31
- 32. Storm Troopers • no diversity • assigned activities Purpose: your assigned duty. Told what to do, when to do it. 32
- 33. The Borg • no individuality • no family/outside interests • no celebrations Purpose: growth and assimilation 33
- 34. Fear Culture 34
- 35. Red Shirt 35
- 37. Role adherence Farm boy Smuggler Princess 37
- 38. Constraining individuals • A developer does... • An ops does ... to the detriment of the team. 38
- 39. Speaking up. 39
- 40. Why? • Change your organization. • Educate peers. • Influence DevOps community. 40
- 41. Key strategies • Explicit. • Informs decision making. • Encapsulates aim and key values. 41
- 42. It takes a thousand voices to tell a single story. — Native American saying 42
- 43. Listen • who is involved? • what is the current state? • cultures? • beliefs? 43
- 45. The language of the culture also reflects the stories of the culture. One word or simple phrasal labels often describe the story adequately enough in what we have termed culturally common stories. To some extent, the stories of a culture are observable by inspecting the vocabulary of that culture. Often entire stories are embodied in one very culture-specific word. The story words unique to a culture reveal cultural differences. Roger C. Shank 45
- 46. Identify Inconsistencies and Defenses 46
- 47. Organizational Learning Chris Argyris and Donald Schon 47
- 48. Theory of Action Theory In Use 48
- 49. Model I Single Loop • encourages defensive behaviors (blame) • Behaviors learned early on • Skilled Incompetence - Aversion to learning 49
- 50. Organizational Defense Routine bypass and coverup 50
- 51. Organizational Malaise • organizational failures, no responsibility • focus on negative • the unimplementable values 51
- 52. Model II Double Loop • slowed reasonings • increased analytics • increased reflection 52
- 53. 53
- 54. 54
- 55. Technology Graphs with overlays 55
- 56. Technology Graphs with overlays Kanban boards 56
- 57. Technology Graphs with overlays Kanban boards Time Tracking 57
- 58. Review • What are Myths? • See the Myths • Speaking up 58
- 59. Thank you ❤ Twitter @sigje Email iennae@gmail.com 59
- 60. DevOps or DevOps not. There is no try. — Yoda 60
- 61. 61