Devops: A History
•
8 likes•4,626 views
DevOps originated from the Toyota Production System which pioneered lean manufacturing practices like just-in-time production and continuous improvement. These concepts influenced early software development methodologies like agile, Scrum, and extreme programming. As software development aimed to deliver value faster, operations struggled to keep up, highlighting the need for closer collaboration between development and operations teams. In 2008, Patrick Debois coined the term "DevOps" to describe this integration. Since then, DevOps adoption has grown significantly, though its core goals of empowering employees, delivering value, and embracing change remain the same.
Report
Share
Devops: A History
- 1. DevOps: A History Nell Shamrell-Harrington @nellshamrell DevOpsDays PDX
- 2. Who Am I? Nell Shamrell-Harrington Software Engineer at Chef @nellshamrell nshamrell@chef.io Proud Graduate of St. Mary’s Academy PDX
- 3. Why a talk about the history of DevOps?
- 4. Doesn’t everybody already know this???
- 5. No
- 6. As DevOps has spread throughout the industry
- 7. DevOps has become overmarketed and hyped
- 8. Context has been lost
- 9. Context is crucial for both understanding and applying DevOps
- 10. Buzzwords!!!
- 13. Where is the signal in the noise?
- 14. To go forward, you must go back - Game of Thrones
- 15. The purpose of this talk is to highlight the origin and context of these buzzwords
- 16. How to they are to relevant to us now and into the future
- 17. Let’s start with a meta-buzzword!
- 19. Meta-buzzword: Scale 18th Century: Craft Production Source: “The Machine that Changed the World” by Womack, Jones, and Roos
- 20. 1785: Honore Blanc introduces interchangeable gun parts Meta-buzzword: Scale Source: “Implementing Lean Software Development” by Poppendieck
- 21. 1908: Henry Ford produces the Model T Meta-buzzword: Scale Source: “The Machine that Changed the World” by Womack, Jones, and Roos
- 22. Interchangeable parts, interchangeable workers Meta-buzzword: Scale Source: “The Machine that Changed the World” by Womack, Jones, and Roos
- 23. “Standardization in its true sense is the union of all the best points of commodities with the best points of production…” - Henry Ford Meta-buzzword: Scale Source: “Today And Tomorrow” by Henry Ford
- 24. “…to the end that the best commodity may be produced in sufficient quantity and at the least cost to the consumer” - Henry Ford Meta-buzzword: Scale Source: “Today And Tomorrow” by Henry Ford
- 25. “Many people thought that machine production would destroy craftsmanship…” - Henry Ford Meta-buzzword: Scale Source: “Today And Tomorrow” by Henry Ford
- 26. “Exactly the reverse has come about; we now need more expert machinists than we have ever needed” - Henry Ford Meta-buzzword: Scale Source: “Today And Tomorrow” by Henry Ford
- 27. Sound familiar?
- 28. “Each of the high performers had server/sysadmin ratios greater than 100:1…” Meta-buzzword: Scale Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford
- 29. “In contrast, analysts report that average server/sysadmin ratios is between 15:1 and 25:1” Meta-buzzword: Scale Source: “The Visible Ops Handbook” by Behr, Kim, and Spafford
- 30. Back to the past!
- 31. Ford Mass Production System designed for huge quantities of limited models Meta-buzzword: Scale Source: “The Toyota Way” by Jeffrey K. Liker
- 32. “Any customer can have a car painted any color that he wants as long as it is black” - Henry Ford Meta-buzzword: Scale Source: “My Life and Work” by Henry Ford
- 34. Lean was originally used to characterize the Japanese approach to automobile manufacturing Meta-buzzword: Lean Source: “Implementing Lean Software Development” by Poppendieck
- 35. 1926: Toyoda Automation Loom Works Meta-buzzword: Lean Source: “The Toyota Way” by Jeffrey K. Liker
- 36. Buzzword: Jidoka
- 37. Automation with a human touch Buzzword: Jidoka Source: “The Toyota Way” by Jeffrey K. Liker
- 38. Sound familiar?
- 39. “…ask yourself, does this alert require any immediate intervention? Alerts should be actionable.” - Patrick Debois Buzzword: Jidoka Source: “Web Operations” by John Allspaw and Jesse Robbins
- 40. “If an alert can be ignored or doesn’t require human intervention, the alert is a waste of energy” - Patrick Debois Buzzword: Jidoka Source: “Web Operations” by John Allspaw and Jesse Robbins
- 41. Back to the past!
- 42. 1930’s: Toyota pivots from looms to automobiles Meta-buzzword: Lean Source: “The Machine that Changed the World” by Womack, Jones, and Roos
- 43. 1940’s: World War II Meta-buzzword: Lean Source: “The Toyota Way” by Jeffrey K. Liker
- 44. Toyota Production System Meta-buzzword: Lean Source: “The Toyota Way” by Jeffrey K. Liker
- 45. “Flexibility required marshaling the ingenuity of workers to continuously improve processes” Meta-buzzword: Lean Source: “The Toyota Way” by Jeffrey K. Liker
- 46. Buzzword: Kaizen
- 47. Continuous Improvement Buzzword: Kaizen Source: “The Toyota Way” by Jeffrey K. Liker
- 48. Buzzword: Kanban
- 49. Kanban “pulls” from the previous step Buzzword: Kanban Source: “The Toyota Way” by Jeffrey K. Liker
- 51. “…only what is needed, when it is needed, and in the amount needed” Buzzword: Just In Time Source: “Just-in-Time” toyota-global.com
- 52. Sound familiar?
- 53. “WIP in the silent killer” Buzzword: Just In Time Source: “The Phoenix Project” by Kim, Behr, and Spafford
- 54. “If no one has slack time, WIP just gets stuck in the system.” Buzzword: Just In Time Source: “The Phoenix Project” by Kim, Behr, and Spafford
- 55. Back to the past!
- 56. Toyota revolutionized manufacturing through lean production Meta-buzzword: Lean Source: “The Toyota Way” by Jeffrey K. Liker
- 57. 1970’s - 90’s: Software Engineering rises to prominence Meta-buzzword: Lean Source: “To Agility and Beyond” by Peter Varyhol
- 59. Buzzword: Waterfall Source: DOD-STD-2167 1985: U.S. Department of Defense adopts software process
- 60. 1. Software requirements analysis Buzzword: Waterfall Source: DOD-STD-2167
- 61. 1. Software requirements analysis 2. Preliminary design Buzzword: Waterfall Source: DOD-STD-2167
- 62. 1. Software requirements analysis 2. Preliminary design 3. Detailed design Buzzword: Waterfall Source: DOD-STD-2167
- 63. 1. Software requirements analysis 2. Preliminary design 3. Detailed design 4. Coding and unit testing Buzzword: Waterfall Source: DOD-STD-2167
- 64. 1. Software requirements analysis 2. Preliminary design 3. Detailed design 4. Coding and unit testing 5. Computer Software Component (CSC) integration and testing Buzzword: Waterfall Source: DOD-STD-2167
- 65. 1. Software requirements analysis 2. Preliminary design 3. Detailed design 4. Coding and unit testing 5. Computer Software Component (CSC) integration and testing 6. Computer Software Component Interface (CSCI) testing Buzzword: Waterfall Source: DOD-STD-2167
- 66. Buzzword: SCRUM
- 67. Buzzword: SCRUM 1995: Sutherland and Schwaber present “The Scrum Development Process” Source: “Scrum Development Process” by Ken Schwaber
- 68. “The development process is regarded as unpredictable at the onset…” - Ken Schwaber Buzzword: SCRUM Source: “Scrum Development Process” by Ken Schwaber
- 69. “…and control mechanisms are put in place to manage the unpredictability” - Ken Schwaber Buzzword: SCRUM Source: “Scrum Development Process” by Ken Schwaber
- 70. “Scrum also defined time-boxed iterative development cycles whose goal was to deliver working software” - Peter Varyhol Buzzword: SCRUM Source: “To Agility and Beyond” by Peter Varyhol
- 71. Buzzword: Agile
- 72. 1996: Extreme Programming project started Buzzword: Agile Source: extremeprogramming.org
- 73. Buzzword: Agile Source: “Writing the Agile Manifesto” by Martin Fowler 2000: Extreme Programming leaders meet in OR
- 74. 2001: Agile Manifesto Written Buzzword: Agile Source: “Writing the Agile Manifesto” by Martin Fowler
- 75. “Our highest priority is to satisfy the customer through early and continuous delivery of valuable software” Buzzword: Agile Source: agilemanifesto.org/principles.html
- 76. “Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage” Buzzword: Agile Source: agilemanifesto.org/principles.html
- 77. “Working software is the primary measure of progress” Buzzword: Agile Source: agilemanifesto.org/principles.html
- 78. Buzzword: DevOps
- 79. 2007: Patrick Debois is working in IT - has to straddle the connection between dev and ops Buzzword: DevOps Source: “The History of Devops” by Damon Edwards
- 80. 2008: Patrick Debois presents “Agile Operation and Infrastructure: How Infra-Agile Are You?” Buzzword: DevOps Source: “A Short History of DevOps” by Richard Rapaport
- 81. “Development and Infrastructure would work in isolation and would integrate just before the political deadline…There was no time left to fix things” Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 82. “Every sprint you would have a new working release and it would constantly improve.” Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 83. “The application went live… Every release they would improve both the software and the infrastructure” Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 84. • Layers of Agile Infrastructure Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 85. • Layers of Agile Infrastructure • Technical Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 86. • Layers of Agile Infrastructure • Technical • Project Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 87. • Layers of Agile Infrastructure • Technical • Project • Operations Buzzword: DevOps Source: “Agile Operations and Infrastructure” by Patrick Debois
- 88. 2009: John Allspaw and Paul Hammond present “10+ Deploys per Day, Dev and Ops Cooperation at Flickr” Buzzword: DevOps Source: “A Short History of DevOps” by Richard Rapaport
- 89. Ops: “It’s not my machines, it’s your code!” Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 90. Ops: “It’s not my machines, it’s your code!” Dev: “It’s not my code, it’s your machines!” Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 91. Ops and Dev have the same job Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 92. Ops and Dev have the same job Enable the business to function Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 93. All businesses require change Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 94. All businesses require change Change involves risk Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 95. Dev and Ops must own this risk through culture and tools Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 96. “Tools will not help you if you install them and still have an argumentative culture going on” Buzzword: DevOps Source: “10+ Deploys per Day…” by John Allspaw and Paul Hammond
- 97. 2009: First DevOpsDays held in Ghent, Belgium Buzzword: DevOps Source: “A Short History of DevOps” by Richard Rapaport
- 98. 2010: First DevOpsDays held in USA Buzzword: DevOps Source: “A Short History of DevOps” by Richard Rapaport
- 99. 2010: #devops takes off on Twitter Buzzword: DevOps Source: “A Short History of DevOps” by Richard Rapaport
- 100. 2016: So much DevOps! Buzzword: DevOps
- 102. The ideals of producing the best product
- 103. In the most humane and engaging way for employees
- 104. Have stayed the same
- 105. The implementations of the ideals have evolved
- 106. And will continue to evolve
- 107. They must continue to be nurtured and cultivated
- 109. History carried the torch this far
- 110. Now it’s your turn
- 111. Carry the ideals onward
- 112. Thank you
- 113. Who Am I? Nell Shamrell-Harrington Software Engineer at Chef @nellshamrell nshamrell@chef.io Proud Graduate of St. Mary’s Academy PDX
- 114. Who Am I? Nell Shamrell-Harrington Software Engineer at Chef @nellshamrell nshamrell@chef.io Proud Graduate of St. Mary’s Academy PDX Any Questions?