Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Destroying DevOps Culture Anti-Patterns

41 views

Published on

DevOps is a set of practices and culture that an organization uses to deliver operational excellence. DevOps should not just be teams, tools, or things you hire a consultant for. In a development or operations practice, an anti-pattern is a behavior that crops up, which hinders the best efforts of a project or organization. Learn to how to identify these DevOps Culture Anti-patterns, and then attack them in specific ways to resolve these issues.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Destroying DevOps Culture Anti-Patterns

  1. 1. DESTROYING DEVOPS CULTURE ANTI-PATTERNS
  2. 2. THIS IS CONFUSING
  3. 3. THIS IS CONFUSING WHY DEVOPS?
  4. 4. A CULTURAL and PROFESSIONAL movement, focused on how we build and operate high velocity organizations, born from the experiences of its practitioners. DEVOPS http://chef.github.io/devops-kungfu/#/
  5. 5. DEVOPS
  6. 6. DEVOPS
  7. 7. CULTURE
  8. 8. WESTRUM CULTURES
  9. 9. PATHOLOGICAL
  10. 10. BUREAUCRATIC
  11. 11. GENERATIVE
  12. 12. GENERATIVE
  13. 13. GOOGLE TEAM ANALYSIS
  14. 14. GOOGLE TEAM ANALYSIS Individual employee optimization isn’t enough to bring success.
  15. 15. How teams interact, work together, and see their work is more important than who is on the team. GOOGLE TEAM ANALYSIS
  16. 16. GOOGLE TEAM ANALYSIS Psychological safety Dependability Structure & clarity Meaning of work Impact of work
  17. 17. PERFORMANCE
  18. 18. LEAN ENTERPRISE
  19. 19. @tomcudd LEAN ENTERPRISE
  20. 20. @tomcudd LEAN ENTERPRISE
  21. 21. ACCELERATE
  22. 22. BEHAVIORS
  23. 23. ACCELERATE
  24. 24. ACCELERATE
  25. 25. KATA
  26. 26. 7 ANTI-PATTERNS
  27. 27. Tribal Knowledge
  28. 28. Tribal Knowledge vs. Increased Collaboration
  29. 29. Super Hero Culture
  30. 30. Super Hero Culture vs. Shared Responsibility
  31. 31. Silos
  32. 32. Silos vs. No Silos
  33. 33. Centralized Decision Making
  34. 34. Centralized Decision Making vs. Autonomous Teams
  35. 35. Quality at the end of the development process
  36. 36. Quality at the end of the development process vs Building Quality into the development process
  37. 37. Information Hoarding
  38. 38. Information Hoarding vs. Feedback
  39. 39. Manual Processes
  40. 40. Manual Processes vs. Automation
  41. 41. ADAPT
  42. 42. CARE AND ACT Care about people, help others, and act upon those feelings and emotions
  43. 43. CHANGE When we can’t change other people, teams, organizations, we change ourselves instead
  44. 44. SUCCESS A successful org has good culture, teams, people, trust, relationships, positive actions.
  45. 45. “Everyone thinks of changing the world, but no one thinks of changing himself.” - Leo Tolstoy

×