LISA 2011 Keynote: The DevOps Transformation


Published on

Published in: Technology, Business
  • OMG... yes! The Operations Management piece confirmed my thoughts about IT & Agile and how to piece it together. 'The Leader's Guide to Radical Management: Reinventing the Workplace..Chapter 6' started me down this journey.(plus all my other reading and research.) Now the trick is to pilot opportunities in a shop of embedded IT & SDLC practices dating back 30 years. Thanks so much Ben!
    Are you sure you want to  Yes  No
    Your message goes here
  • Holy cow. Great presentation, Ben. Patrick DeBois and I are studying your presentation right now as we're working on 'DevOps Cookbook.' I'm a big fan of Boyd's OODA loop, by the way. Talk to you soon!

    Many thanks for all your critical feedback that you've sent. Your kung fu is fantastic!
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

LISA 2011 Keynote: The DevOps Transformation

  1. Ben Rockwood Director of Systems Engineering Joyent, Inc.TheDevOpsTransformation From here to there and whyThursday, December 8, 2011
  2. Section 1 What is DevOps?Thursday, December 8, 2011
  3. DevOps is a cultural and professional movement. Adam JacobThursday, December 8, 2011
  4. It’s not a tool (thing).Thursday, December 8, 2011
  5. It’s not a title (person).Thursday, December 8, 2011
  6. It’s not just dev & ops.Thursday, December 8, 2011
  7. CAMS • Culture • Automation • Measurement • Sharing John WillisThursday, December 8, 2011
  8. It’s a banner for change.Thursday, December 8, 2011
  9. Re-envisioning the IT World “We are the music makers, And we are the dreamers of dreams,” Arthur OShaughnessy (1874) The world is changable, if we only have the courage to break with the status quo (overcome inertia)Thursday, December 8, 2011
  10. Pro Tip #1 DevOps is a journey of discovery, not a destination.Thursday, December 8, 2011
  11. Pro Tip #1 DevOps is a journey of discovery, not a destination. Please join the global conversation!Thursday, December 8, 2011
  12. Section 2 DevOps Deconstruction • Collaboration of People • Convergence of Process • Creation & Exploitation of Tools In that order, not the reverse.Thursday, December 8, 2011
  13. Simon Sinek’s Golden Circle Why How you do it What you do Ted Talk: Simon Sinek: How great leaders inspire action”Thursday, December 8, 2011
  14. Simon Sinek’s Golden Circle Motivation, Values, Belief Why (Both make up the limbic brain, feelings, behavior, decision making, no language) Method How What Product (Maps to Neo-Cortex; Rational Thought & Language)Thursday, December 8, 2011
  15. Golden Circle in DevOps 1: Quality through Collaboration is our motivation Why? 2: Process & Tools is how How? What? 3: Build awesome servicesThursday, December 8, 2011
  16. DevOps Done Wrong 3: To improve efficiency of infrastructure management Why? 2: Building Process around automation How? What? 1: Automate using Configuration ManagementThursday, December 8, 2011
  17. “Why is the only true source of power. Without it you are powerless.”Thursday, December 8, 2011
  18. Ackoff’s 5 Contents of the Mind Wisdom Understanding Knowledge Information DataThursday, December 8, 2011
  19. Wisdom Insight Understanding Why Knowledge How to Who, What, When, Where Information How much.. DataThursday, December 8, 2011
  20. Architect Wisdom Insight Systems Understanding Why Engineer Knowledge How to Jr SA/Support Who, What, When, Where Information How much.. DataThursday, December 8, 2011
  21. Systems Thinking Synthesis Wisdom Insight Understanding Why Analysis Knowledge How to Who, What, When, Where Information How much.. DataThursday, December 8, 2011
  22. Systems Thinking • Systems Thinking is concerned with the interaction of the parts to form a whole • Systems Dynamics is concerned with the feedback loops between the parts • “A system can not understand itself.” -W. Edwards DemingThursday, December 8, 2011
  23. Pro Tip #2 DevOps starts with why, with a holistic vision, and supports that vision with process and tools.Thursday, December 8, 2011
  24. Section 3 Dev Ops Should be this.Thursday, December 8, 2011
  25. Dev Ops The reality is usually this.Thursday, December 8, 2011
  26. The Value Stream Requirements Dev Software Ops ServiceThursday, December 8, 2011
  27. Silo’ed Priorities Get it out on time, no defects. Get it up. Keep it up. Cheap. Requirements Dev Software Ops Services +NFR Goods ServicesThursday, December 8, 2011
  28. Who’s responsible for quality?Thursday, December 8, 2011
  29. What is Quality? • ISO-9000: "Degree to which a set of inherent characteristics fulfills requirements." • Dr. Juran: "Fitness for use." • Crosby: "Conformance to requirements." • 6 Sigma: "Number of defects per million opportunities." And you wonder how we used waterfall so long....Thursday, December 8, 2011
  30. What is quality really? • The degree to which a good or service is what the customer expects it to be. • Examples: The Big Mac,Velveeta, SteakThursday, December 8, 2011
  31. Quality Software • Does what it purports to do • Is intuitive and easy to use • Is quick and responsive; given the task • Observable (“Whats it doing?!”)Thursday, December 8, 2011
  32. Quality Service • Does what it purports to do • Is intuitive and easy to use (Friendly) • Is quick and responsive; given the task • Observable (“Whats it doing?!”) • Available • Self-Service if possibleThursday, December 8, 2011
  33. “Efficiency is doing things right; effectiveness is doing the right things.” Peter DruckerThursday, December 8, 2011
  34. Pro Tip #3 Quality is a result effectiveness of the interactions across the entire value stream.Thursday, December 8, 2011
  35. Section 4 Agile Manifesto Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan 2001Thursday, December 8, 2011
  36. Agile Advantages • Non-Prescriptive • Simple philosophy became an umbrella • Applies to both the developer and the product management alike • Widely known and easy to grok.Thursday, December 8, 2011
  37. IT Service Management • Control Objectives for Information and related Technology (CobiT) • Capability Maturity Model Integration (CMMI) for Service • IT Infrastructure Library (ITIL) • ISO Standards: 20K, 27001, 38500 • NIST SP800-53, PCI DSS, FIPS 200, TIA-942Thursday, December 8, 2011
  38. Making Sense of ITSM SOX Auditing COSO SAS70 ISO 20K Governance Framework CobiT ISO 38,500 Best Practice .... Security Controls ITIL ISO 27K PMBOK NIST SP800-53 PRINCE2 PCI-DSS ASL FIPS 200 BISL ...Thursday, December 8, 2011
  39. Problems with ITSM • Compliance Driven • Security Focused • Complex, Complicated, and Bureaucratic • Pushed down from the top on already over- burdened staff • Consultant Heavy • Hard to grok. Most info 2nd hand.Thursday, December 8, 2011
  40. IT Infrastructure LibraryThursday, December 8, 2011
  41. ITIL Advantage • Most complete & respected pattern for IT • Source for Change Management, Event/ Incident/Problem Management, CMDB, etc. • Provides a common terminology for IT • Chock full of good ideas! Why reinvent the wheel? Guru session on ITIL, Thursday @ 3:30!Thursday, December 8, 2011
  42. Visible OpsThursday, December 8, 2011
  43. The rules don’t make RPGs fun... the DM does. It’s all about how you use the rules.Thursday, December 8, 2011
  44. ITSM in Perspective • No idea should be rejected without consideration • Don’t view it as “all in” or “all out” • Educate yourself on them (many are free) and use it however is most appropriate for your team/organizationThursday, December 8, 2011
  45. Ars Gratia Artis • Art for the Sake of Art • Only satisfies a select few The Fountain by Marcel DuchampThursday, December 8, 2011
  46. Pro Tip #4 Agile & ITSM are both sources from which to draw strength, but never at the expense of your vision.Thursday, December 8, 2011
  47. Section 5 Cloud Changed the GameThursday, December 8, 2011
  48. IT Paradigm Shifts • Virtualization stops being about consolidation and begins enabling self- service, automated infrastructure without bare metal constraints • HPC becomes less interesting • Role of the OS changes • Broad platform standardization becomes realisticThursday, December 8, 2011
  49. Dev Paradigm Shifts • Dev can bypass IT at will • Dev has more experience with the APIs that drive cloud than IT (typically) • The Great Leveler; anyone can be a player • SCRUM, Continuous Integration, etc. speed up rate of deploymentThursday, December 8, 2011
  50. “The Rift” Surfaces • Increased awareness of IT and “Web Operations” sub-culture rift • Migration of services from heavy iron into virtualized environments changes more than expected • Over-specialization becomes an issue • X86 Management is differentThursday, December 8, 2011
  51. Rise of the Tools • Commercial & Open Source “Build your own cloud” solutions speed up • Puppet & Chef arrive alongside CFengine to tame the new complexity • “Infrastructure As Code” starts looking realistic, as tools are more about CM than deployment • SaaS allows IT teams to offload undesirable or complex components. (ex: PagerDuty)Thursday, December 8, 2011
  52. Vagrant • Create test/dev environments on your laptop • Configure with CM • An excellent method for using Operations “Infrastructure as Code” to empower dev, ops, qa, etc.Thursday, December 8, 2011
  53. Pro Tip #5 The Cloud is here to stay, and its awesome. Contrary to popular belief, it will generate MORE demand for SA’s, not less.Thursday, December 8, 2011
  54. Section 6 Operations Management “Operations management is an area of management concerned with overseeing, designing, and redesigning business operations in the production of goods and/or services.” WikipediaThursday, December 8, 2011
  55. What is Operations? Executives Finance Operations Marketing Operations is doing what you do.Thursday, December 8, 2011
  56. OM Subjects • Operations • Quality Strategy Management • Product & Service • Forecasting Development • Wait-Line Theory • Project • Scheduling Management • Process • LEAN Measurement • Six Sigma • Financial Analysis • TOC ...and more.Thursday, December 8, 2011
  57. A Brief History of Operations Management Understanding the genesis of the ideas we now take for granted as common sense.Thursday, December 8, 2011
  58. Fredrick Winslow Taylor • “The Principles of Scientific Management” (1911) • Applied scientific method to work. • Generally blamed for everything.Thursday, December 8, 2011
  59. Henry Ford • Father of “Mass Production” • Built the Model T from 1908 ($850, $20K) to 1927 ($290, $3K). • No formal education, worked at Edison Co from 1891 to 1899.Thursday, December 8, 2011
  60. Alfred Sloan • President of GM in 1923 • Did for big management what Ford did for manufacturing • Involvement with MIT later became the Sloan Business School. • BS EE from MITThursday, December 8, 2011
  61. Sakichi Toyoda • Started Toyoda Automatic Loom Works 1927 • Invented Jidoka (autonomous automation) [Fault Management], and “5 Whys” • Started making cars in 1933Thursday, December 8, 2011
  62. W.A. Shewhart • Invented PDSA Continuous Improvement Cycle • Worked at Bell Labs from 1925 to 1956 • Father of Statistical Process Control • PhD in PhysicsThursday, December 8, 2011
  63. W. Edwards Deming • Student of Shewhart • Sent to Japan after WW2 and taught the Japanese (1950) • Father of the Quality movement • Ignored in US until late 1970’s • BS EE, MS/PhD MathThursday, December 8, 2011
  64. Taiichi Ohno • Created the Toyota Production System in late 1940’s, refined through the 1950’s • Father of Just-in-Time, Kanban, etc. • Learned from Ford’s book “Today & Tomorrow” & DemingThursday, December 8, 2011
  65. Shigeo Shingo • Technical man behind TPS • Father of SMED, Poka- Yoke (“mistake- proofing”), “Zero Quality Control”, etc.Thursday, December 8, 2011
  66. Damon Edwards Israel Gat, December 8, 2011
  67. Peter Drucker • Father of Modern Management • Wrote 39 management books between 1939 and 2005Thursday, December 8, 2011
  68. Ludwig von Bertalanffy • Father of Systems Theory • Wrote “General Systems Theory”, published in US following WW2.Thursday, December 8, 2011
  69. Russell Ackoff • Friend of Deming • Pioneer in Operations Research (OR) in 1957 and Systems Theory • (imho, the Feynman of OR) • BS Architecture, PhD Philosophy of ScienceThursday, December 8, 2011
  70. Armand V. Feigenbaum • Coined the term “Total Quality Control” (1961), which later became “Total Quality Management” (TQM) • Together with Deming and others ideas, became basis for ISO-9000 • PhD Econ MITThursday, December 8, 2011
  71. The US Decline • 1973 Oil Crisis deals a nasty blow to the US Mass Production system • Japanese weather the storm thanks to Kanban (Just in Time; Toyota Production System) • In 1980’s Japanese quality puts US to shame • Deming in NBC documentary in 1980, publishes first book in 1983Thursday, December 8, 2011
  72. Eliyahu Goldratt • Created the “Theory of Constraints” • Published in his novel “The Goal” (1984) • Applied TOC to other areas such as project management (“Critical Chain”), sales (“Mafia Offer”), etc.Thursday, December 8, 2011
  73. James Womack, et al • Coined “Lean” in 1988 HBR Article. • Becomes “The Machine that Change the World” (1990) which brought TPS to the masses.Thursday, December 8, 2011
  74. On the Shoulders of Giants • There is a continuous chain of ideas being condensed and re-applied again and again throughout the 20th Century. • Today its largely rolled into “Lean” • Many of our “new” ideas are not new at all, they are new applications of proven ideas that are simply new to this field. • Many of the OM pioneers were geeks.Thursday, December 8, 2011
  75. Thursday, December 8, 2011
  76. Pro Tip #6 “Those who cannot remember the past are condemned to repeat it” George Santayana These things aren’t going away, a little education will serve you for years to come.Thursday, December 8, 2011
  77. The 3 Aspects of DevOps dev>OPS DEV<ops DEV<>OPSThursday, December 8, 2011
  78. dev>OPS • Operations centric focus on DevOps • Adopts “Infrastructure as Code” ideal • Considers SCRUM, Kanban, and Agile Operations Concepts • Gets serious about metrics and holistic/ qualitative monitoringThursday, December 8, 2011
  79. DEV<ops • Development centric focus on DevOps • Adopts continuous deployment • Embedded metrics and increased focus on operational performance • Dev’s learn about operational challengesThursday, December 8, 2011
  80. DEV<>OPS • Full collaboration between teams • Boundaries between them blur • Both teams are accountable, full participation in emergencies and postmortem meetings • Dev access to prod environment • Joy.Thursday, December 8, 2011
  81. Transitioning • If at all possible, go directly to DEV<>OPS and grow together • If not, do what you can to set the stage, measure results and make allies to build a case for management support.Thursday, December 8, 2011
  82. The Most Powerful Tool in the DevOps Arsenal?Thursday, December 8, 2011
  83. Thursday, December 8, 2011
  84. Other Tools to Start • Office Hours • Sit together • Join the other teams meetings • Ask lots of questions • Implement the “No Asshole Rule” • Have funThursday, December 8, 2011
  85. Pro Tip #7 If it ain’t fun, it ain’t workin’.Thursday, December 8, 2011
  86. Collaboration of People Convergence of Process Creation & Exploitation of Tools * Measure Everything * Have a systems view * Focus on effectiveness & quality * Learn from others and the past * Encourage pride of workmanship (fun)Thursday, December 8, 2011
  87. Thank You.Thursday, December 8, 2011
  88. Twitter:@patrickdebois@botchagalupe Join the@damonedwards@allspaw Conversation!@RealGeneKim@jordansissel@portertech@lusis @LordCope@jamesurquhart Websites:@puppetmasterd@netik @markimbriaco, December 8, 2011