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.

Devops is a verb its all about feedback

14,672 views

Published on

Presentation done at @atlasisian Summit

Published in: Technology, Business
  • Be the first to comment

Devops is a verb its all about feedback

  1. Devops is a verbIt’s all about feedbackPatrick DeboisHosted Operations, On Demand Platform, Atlassian
  2. Your Business
  3. Rough Times
  4. Competitors
  5. You care
  6. “Are we doing the right thing?”
  7. “How can we improve?”
  8. A tribute toNorbertWiener
  9. Anti-Aircraft Fire Control Bring down that AircraftBusiness
  10. Anti-Aircraft Fire Control Let’s calculate the correct angleBusiness Developers
  11. Anti-Aircraft Fire Control This is how you shoot: ...Business Developers Operations
  12. Anti-Aircraft Fire Control Let’s try these coordinatesBusiness Developers Operations
  13. Anti-Aircraft Fire Control Shit. It’s flying to fast, changed direction. We totally missed it.Business Developers Operations
  14. Anti-Aircraft Fire Control Few casualties. Please help us!Business Developers Operations Customers
  15. Anti-Aircraft Fire Control Will they ever get the coordinates right?Business Developers Operations Customers
  16. Anti-Aircraft Fire Control Will they ever learn how to shoot correctly?Business Developers Operations Customers
  17. Anti-Aircraft Fire Control How can it be so hard? Try again!Business Developers Operations Customers
  18. Anti-Aircraft Fire Control X Tries laterBusiness Developers Operations Customers
  19. Anti-Aircraft Fire Control Major CasualtiesBusiness Developers Operations Customers
  20. Solved, by faster feedback!Business Developers Operations Customers Solved, by integrating technology
  21. DEVOPS
  22. DEV/OPS
  23. DEV OPSaka Project aka Production
  24. Plan DEV OPS
  25. BuildPlan DEV OPS
  26. BuildPlan DEV Test OPS
  27. BuildPlan DEV Test OPS Improve
  28. BuildPlan DEV Test OPS Improve People: Agile Manifesto Process : Scrum, Kanban, Scrumbut Tools: Unittest, CI build Systems
  29. DEV Plan OPS
  30. RunDEV Plan OPS
  31. RunDEV Plan OPS Monitor
  32. RunDEV Plan OPS Monitor Improve
  33. RunDEV Plan OPS Monitor ImprovePeople: *-litiesProcess: ITIL, First level , HelpdeskTools: Monitoring, Provisioning, Logging
  34. First Order Feedback loops Build RunPlan DEV Test Plan OPS Monitor Improve Improve
  35. “Silo” Thinking IncreaseBusiness Value DEV OPS
  36. “Silo” Thinking IncreaseBusiness Value DEV OPS Protect Business Value
  37. Dreamer Realist Critic DEV OPSThree Phases of Creativity (Disney)
  38. “Devops” Practices Increase IncreaseBusiness Value Business Value DEV OPS Protect ProtectBusiness Value Business Value
  39. Driver #1Increase Productivity Agile development DEV OPS
  40. Driver #1Increase Productivity Agile development DEV OPS Driver #2 Large scale Infrastructure
  41. IncreaseBusiness Value DEV CLASH OPS Protect Business Value
  42. Reactions: Continuous DeliveryDEV CLASH OPS
  43. Reactions: Continuous DeliveryDEV CLASH OPSApplication Lifecycle Management
  44. Business Customer Deliver Value
  45. Business Customer Lean Value Chain
  46. From idea to value Idea Value Devops AgilePractices Lean Product Operations DevelopmentPrinciples Lean (End-to-End Flow) Matthias Marschall https://cacoo.com/diagrams/uapwdcN6SDfwClDY
  47. Sonar your value DevopsPractices Lean Product Development Operations
  48. Identify bottleneck(s)Business Customer Value Stream Mapping
  49. where’s the bottleneck? HR MGMT FINBusiness SALES DEV OPS Customer .....
  50. In Dev & Ops ? HR MGMT FINBusiness SALES DEV OPS Customer .....
  51. Or elsewhere? •Do you have the correct Hiring Policy? (HR) •Are you overselling? (Sales) •Correct Financial Icentives? (FIN)“devops” bottlenecks can live outside dev or ops
  52. Where to start?
  53. Boundary Objects DEV OPSDeployment Monitoring Logging Packaging ... http://en.wikipedia.org/wiki/Boundary_object
  54. Symmetry of Ignorance/ArroganceDEV OPS http://www.jedi.be/blog/2012/01/08/devops-a-wicked-problem/
  55. “Devops Areas”a way to ‘categorize’ practices
  56. Culture AutomateDEV OPS Measure Share http://www.opscode.com/blog/2010/07/16/what-devops-means-to-me/
  57. Area 1: Extend delivery to production ‘think Jez Humble” Area 1DEV OPS
  58. Area 1: Extend delivery to Production • Ability to rebuild your production from source • Infrastructure as code • Version controlled • Reuse across dev, test, prod Tools Faster feedback on production issues
  59. Area 1: Extend delivery to Production• Visualize production work done • Track production tasks (Kanban, Scrim) • Time spent on production issues are put on the sprint backlog Process Better estimates and feedback on effort
  60. Area 2: Extend operations feedback to project think “John Allspaw” DEV OPS Area2
  61. Area 2: Extend operations feedback to project • make monitoring, logs, metrics available to project to see information • give access to production systems Process ToolsSelf service the ability to ‘see’ prod
  62. Area 2: Extend operations feedback to project • blameless postmortems together with dev • root cause analysis • identify recurring problems People ProcessIntegrate feedback to avoidsame mistakes
  63. Area 3: Embed Project knowledge into Operations Area 3 DEV OPS
  64. Area 3: Embed project knowledge into operations • Devs wear pagers for production • After a release, devs stay responsible for X months for all alerts People ProcessTake production experienceback to avoid things earlyin the process
  65. Area 4: Embed Operations knowledge into Project DEV OPS Area 4
  66. Area 4: Embed operations knowledge in project • Ops are part of the project team • Attend stand-ups • Work on backlog issues • Part of planning meetings People ProcessEarly feedback by prevention
  67. Area 3: Embed Project knowledge into Operations Area 1: Extend delivery to productionDEV OPS Area 2: Extend operations feedback to project Area 4: Embed Operations knowledge into Project
  68. Area 3: Embed Project knowledge into Operations Area 1: Extend delivery to productionDEV OPS Area 2: Extend operations feedback to project Area 4: Embed Operations knowledge into Project
  69. “Areas” vs “Steps” non-prescriptive: you can start in any area location ofyour bottleneck/solution may vary
  70. “Layers per Area” Can you ‘technically’ ToolsArea X do it Process Should you do it People Will you do it (culture) things you do in an area (think ‘tags’)
  71. With great power comesgreat responsibility Voltaire
  72. Area Maturity Level a way to track your journeyhttp://groups.google.com/group/devops/browse_frm/thread/f3de603a4cea493e?scoring=d&
  73. CMMI Maturity Levels (Process Centric) Unpredictable Initial poorly controlled and reactive Focused on project, often Managed and reactive Focused on organization and Defined proactive Quantitatively Managed Measured and controlled Focus on Optimizing Improvement
  74. “Alternative Maturity Levels” (cfr. Continuous Integration Model) Intro Using Source Control ... Builds Triggered by Novice Commit ... Automated Deployment Intermediate to Testing ... Automated Functional Advanced Testing ... Continuous Deployment Insane to Prod ...http://blogs.urbancode.com/continuous-integration/continuous-integration-maturity-model/
  75. Devops ‘self assessment’ Tools Process People Area1 Defined Defined Defined Area2 Undefined Defined Undefined Area3 Optimizing Undefined Undefined Area4 Undefined Undefined Undefined
  76. Just don’t fool yourself Me and many others
  77. Faster and better feedbackDEV OPSSmaller and more frequent changes
  78. Speed indicatorsDeploy Change Requests People involvedper day per day per deploy People Tools Process
  79. How fast can you ? vsHow fast do you want to go ?
  80. Area 1: Extend delivery to Production• A new developer can deploy to prod from day1 • We are confident our tests will stop him • We trust people to do the right thing Process At the insane level, really?
  81. Tests are the brakes thatmake us go faster
  82. The new bottlenecks• Testers (QA)• Risk Control (Security)• Standardize and automate• Use human knowledge ‘embedded’ in teams• Peer reviews• Flag areas of risk for review
  83. The networking modelNewspapers control Silos Cross functionalSocial Media sharing teams
  84. Deploy vsRelease
  85. “Canary” releases“Dogfooding” environments
  86. Mean Time Between Failureis an outdated metric
  87. Mean Time To Recoveris the new gold
  88. How fast can you respond?
  89. twitter - #devops irc - #infratalk podcast - http://devopscafe.org conference - http://devopsdays.org http://groups.google.com/group/devopshttp://groups.google.com/group/devops-toolchain
  90. The DevOps Cookbook Coming in July 2012 - Signup at http://itrevolution.com
  91. Thank you!

×