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.

Bootstrapping a devops mentality - At Skillsmatter by Patrick Debois


Published on

Don't expect tools. It's a human problem

Published in: Technology, Business

Bootstrapping a devops mentality - At Skillsmatter by Patrick Debois

  1. a devops mentality @patrickdebois
  2. Thank you!
  3. devops Cultural and Professional Movement Adam Jacob
  4. My Background• Independent consultant• Have worked in different roles• Agile and Infrastructure• Just Enough Developed Infrastructure -• Started organizing devopsdays• Recently joined Cutter Consortium
  5. Background check?analysts databasedeveloper securityoperations middlewaretesters salesnetwork managerstorage hr people
  6. The movement is inclusive Awesome Happy Cool Built neat stuff! Adam Jacob
  7. There are exclusive people Grumpy Tool Centric Us vs Them I’m a devop you’re a sysadmin Adam Jacob
  8. Looking for tools?
  9. Looking for tools?You can still leave ...
  10. DEV OPS The problem
  11. “It’s NOT a technical problem”
  12. “It’s a human problem”
  13. We don’t trust We don’t trust the guys from the guys from operations. development. They suck They suck We don’t trust the guys from management. They suck
  14. Premise today“It’s a trust problem”
  15. Starting a devops culture = restoring trust
  16. Traditional Business Formula(Strategy X Execution)= Results
  17. Factor(Strategy X Execution)* Trust = Results
  18. of Trust(-) Trust = (-) Speed (+) Cost(+) Trust =(+) Speed!(-) Cost!
  19. Tax Dividend• 10 x 10 = 100 (- Tax 40 %) = 60• 10 x 10 = 100 (- Tax 10 %) = 90• 10 x 10 = 100 (+ Div 20%) = 120
  20. Trust = f(character, competence)
  21. Waves of Trust Self Relationship Organizational Market Societal
  22. 1. Self Trust
  23. “We trust people,who make things happen”
  24. But ...Can otherstrust you?
  25. “We judge others by their behavior,we judge ourselves by our intentions”
  26. Principle of Credibility “The 4 Cores”• Trust = f(character, competence)• Character = f(integrity, intent)• Competence = f(capabilities, results)
  27. CapabilityTalentsAttitudesSkillsKnowledgeStyle
  28. Ah, so this is where the (cool)tools come in !
  29. Chef Ruby Mysql LinuxPuppet Java Redis Mac OSX Event EC2MachineNode.js I <3 technology Vmware Fog Nginx Vagrant SinatraJclouds Thin Virtualbox Rails
  30. Craftsmanship
  31. Technology ManagementBut there’s a *lot* moreSocial Financial Communication
  32. WTF, do I need to learn all that?
  33. Broader knowledge,will make your actions more balanced
  34. It’s NOT about devstaking over ops or ops taking over devs.
  35. It’s about collaborationwith people you trust.
  36. Results:• Take responsibility for results not just your action. Avoid , my job is only to ...• Expect to finish the job• Finish strong
  37. Bootstrapping
  38. Make a personal backlog• Plan an item you can really make happen • No too big, make it feasible• (Result)Define what you want to achieve• (Competence)Learn what you need• Do : trust comes if you make things happen• Check the result• Act on it
  39. As a person• I want to develop these capabilities• I want to achieve results• When I fail , I want to learn and improve!
  40. As a manager, I want to • help people develop these capabilities • help people achieve results • (support the people) • help people fail and learn and improve!(+) Trust =(+) Speed!(-) Cost!
  41. 2. Relational Trust
  42. Reach out to others
  43. Agile already did a great job
  44. Get together find allies forward links organize meetups distribute books find people with real issueskindly ignore nay sayers (for now)
  45. You can use technology to get theconversation started• Continuous Delivery • Testing, Monitoring• Automation • Fixing a problem• Scalability • Infrastructure as code• Performance • <whatever>
  46. “Seek to establish trust” Technology Trust by Testing, Monitoring Human Trust by Behavior
  47. 13 Behaviors “trust is established through action”• Needs to be • Sweet Spot balanced (Strength)• Too Little • Too much (Weakness) (Weakness)• f.i. talk straight vs demonstrate respect
  48. #1 Talk Straight • We really need this tool vs I want to learn this tool • It needs to be finished by X (that leaves me some time) • The user/my boss wants this now • It’s urgent, it’s important
  49. #2 Demonstrate Respect • we judge a person’s character, by how he treats people who can’t help or hurt him • little things , making things helpful
  50. #3 Create Transparency• no more Bob’s directory• check in your code• expose logfiles, config files ...• visualize progress (Kanban, Burndown)• share your information• make results repeatable
  51. #4 Right wrongs“to know what is right and not todo it is the worst cowardice” - Confucius • when you know there is a short cut, fix it and don’t leave it • fix a bug when it occurs, write a test • fix it, fix it all the way
  52. #5 Show loyalty • give credits • talk as if people were present • represent others
  53. #6 Deliver Results• Clarify Results upfront • your definition vs my definition• Small steps = Validation test (Userstories)
  54. #7 Get Better “Illiterate are those who can not learn, unlearn, relearn” - Alvin Toffler• seek feedback (Retrospectives)• learn from mistakes (5 whys)• ask: what to continue, what to stop, what to start now!• metrics (Neutral , not emotional)• change the system (Systems Thinking)
  55. #8 Confront Reality• avoid 99% finished• burn down chart• only measure of progress is working software (in production)
  56. #9 Clarify Expectations • deadlines vs. cut corners (win-win or no deal), negotiate them (who vs trust) • talk to devs, what do they expect • talk to admins, what do they expect • talk to customers
  57. #10 Practice Accountability • Accountability requires facing Truth • yourself and others • Don’t blame others , no pointing fingers
  58. #11 Listen First“If there is any secret, it lies in the abilityto put yourself in the other person’s place” - Henry Ford
  59. #12 Keep Commitments• don’t PR your way out• make them careful• group is committed to results (not manager)• mgt supports team to keeping commitments
  60. #13 Extend Trust • Make it an action • here is the password • here is the code • everybody can check in and deployed to prod (with tests :)remember it’s inclusive not exclusive!
  61. As a person,• Given my capabilities• I want to practice these 13 behaviors• Help others to practice these 13 behaviors
  62. As a manager, I want to encourage behavior that increases trust(+) Trust =(+) Speed!(-) Cost!
  63. “Don’t change culture, change behavior!”
  64. Organizational Trust Eli mi na• Redundancy te Ta xe• Bureaucracy s• Politics• Disengagements (quit and stay)• Turnover (employee)• Churn (stakeholders)• Fraud
  65. Interesting Books
  66. Want to know more? #devops on twitter & irc devops googlegroupdevops-toolchain googlegroup
  68. Thank you!Patrick Debois - - @patrickdebois