1 00:00:07,089 --> 00:00:09,300 After watching this video, you will be able to: 2 00:00:09,300 --> 00:00:14,230 List key examples of DevOps growth that occurred from 2007 to 2019, 3 00:00:14,230 --> 00:00:19,230 and summarize the contributions of key influential people in the growth of DevOps. 4 00:00:19,230 --> 00:00:24,640 I’d like to take you through a brief history of some significant events in the early DevOps 5 00:00:24,640 --> 00:00:28,440 movement and point out who the key influencers were. 6 00:00:28,440 --> 00:00:34,719 DevOps really started in 2007 when Patrick Debois recognized that Dev and Ops were not 7 00:00:34,719 --> 00:00:36,480 working well together. 8 00:00:36,480 --> 00:00:40,260 He wondered if there was a better way. 9 00:00:40,260 --> 00:00:45,640 The next year, at the 2008 Agile Conference, Andrew Clay Shafer created a birds of a feather 10 00:00:45,640 --> 00:00:48,760 meeting (BoF) to talk about “Agile Infrastructure”. 11 00:00:48,760 --> 00:00:54,110 Shafer didn't think anybody would come, so he did not show up to his own meeting. 12 00:00:54,110 --> 00:00:58,460 Patrick Debois showed up and Patrick went looking for Andrew because he wanted to talk 13 00:00:58,460 --> 00:01:03,862 about Agile infrastructure being the solution to get operations to be as Agile like the developers 14 00:01:03,862 --> 00:01:04,663 were. 15 00:01:04,663 --> 00:01:07,183 This is where DevOps got started. 16 00:01:07,978 --> 00:01:14,679 Then in 2009 at the Velocity conference, John Allspaw gave a talk about “10 plus deploys 17 00:01:14,679 --> 00:01:20,384 per day - Dev and Ops Cooperation at Flickr,” and the idea started gaining traction. 18 00:01:20,384 --> 00:01:25,721 This talk made people take notice of what was possible by adopting these early DevOps 19 00:01:25,721 --> 00:01:27,052 practices. 20 00:01:27,263 --> 00:01:32,210 Also in October of 2009, Patrick Debois, often called “The Father of DevOps,” held the 21 00:01:32,210 --> 00:01:35,649 first DevOpsDays conference in Ghent, Belgium. 22 00:01:35,649 --> 00:01:40,390 It was described as, “The conference that brings development and operations together.” 23 00:01:40,390 --> 00:01:43,289 This is where the term "DevOps" was first used. 24 00:01:43,289 --> 00:01:48,380 DevOpsDays is now a local conference held internationally several times a year in different 25 00:01:48,380 --> 00:01:49,439 cities. 26 00:01:49,439 --> 00:01:55,779 In 2010, Jez Humble and David Farley wrote a groundbreaking book called Continuous Delivery 27 00:01:55,779 --> 00:02:00,939 that sets out the principles and technical practices that enable rapid, incremental delivery 28 00:02:00,939 --> 00:02:06,459 of high-quality, valuable new functionality to users using a technique called Continuous 29 00:02:06,459 --> 00:02:08,020 Delivery. 30 00:02:08,020 --> 00:02:12,209 Through automation of the build, deploy, and test process, along with improved collaboration 31 00:02:12,209 --> 00:02:17,069 between developers, testers, operations, delivery teams can release changes in a matter 32 00:02:17,069 --> 00:02:22,319 of hours—sometimes even minutes—no matter the size of the project or the complexity. 33 00:02:22,657 --> 00:02:27,719 This book is over 10 years old, but it still has a lot of great concepts that helped changed 34 00:02:27,719 --> 00:02:33,730 a lot of people's thinking about how to perform software delivery in a continuous fashion. 35 00:02:35,134 --> 00:02:41,609 In 2013, Gene Kim, along with Kevin Behr and George Spafford published The Phoenix Project, 36 00:02:41,609 --> 00:02:44,980 a book based on Elijah Goldratt’s book, The Goal. 37 00:02:44,980 --> 00:02:48,170 The Goal is about a manufacturing plant that is about to go under and what they had to 38 00:02:48,170 --> 00:02:49,189 do to bring it back to life. 39 00:02:49,189 --> 00:02:52,730 It is a story about lean manufacturing principles. 40 00:02:52,730 --> 00:02:56,690 The Phoenix Project is about an information technology (IT) shop in a company that is 41 00:02:56,690 --> 00:03:00,010 about to go under and what it took to bring it back to life. 42 00:03:00,010 --> 00:03:06,640 This story is about applying lean manufacturing principles to software development and delivery. 43 00:03:06,640 --> 00:03:14,739 In 2015, Dr. Nicole Forsgren, Gene Kim, and Jez Humble founded a startup called DORA (DevOps 44 00:03:14,739 --> 00:03:19,359 Research and Assessment) that produced what are now the largest DevOps studies to date 45 00:03:19,359 --> 00:03:21,260 called the State of DevOps Report. 46 00:03:21,260 --> 00:03:24,329 Nicole was the CEO and is an incredible statistician. 47 00:03:24,329 --> 00:03:28,969 Through this research, she found that taking an experimental approach to product development 48 00:03:28,969 --> 00:03:34,450 can improve your IT and organizational performance and that high-performing organizations are 49 00:03:34,450 --> 00:03:38,900 decisively outperforming their lower-performing peers in terms of throughput. 50 00:03:38,900 --> 00:03:43,670 The research shows that undertaking a technology transformation initiative can produce sizeable 51 00:03:43,670 --> 00:03:46,209 cost savings in any organization. 52 00:03:46,209 --> 00:03:51,980 If you haven't read this year’s State of DevOps report, I strongly urge you to do so. 53 00:03:51,980 --> 00:03:54,829 The DevOps Handbook was published in 2016. 54 00:03:54,829 --> 00:03:59,849 It was written by Gene Kim, Jez Humble, Patrick Debois, and John Willis as a follow-on to 55 00:03:59,849 --> 00:04:04,316 The Phoenix Project and it serves as a practical guide on how to implement the concepts that were 56 00:04:04,316 --> 00:04:05,586 introduced in that book. 57 00:04:06,129 --> 00:04:10,519 John Willis, by the way, worked at Docker and Chef back then, and is a DevOpsDays coordinator 58 00:04:10,519 --> 00:04:15,579 after being at the original DevOpsDays in Ghent 2009 with Patrick Debois. 59 00:04:15,579 --> 00:04:19,549 If you only read one DevOps book, this is the book to read. 60 00:04:19,549 --> 00:04:24,000 They looked at companies that have adopted DevOps and document what did work and what 61 00:04:24,000 --> 00:04:24,762 did not work. 62 00:04:24,762 --> 00:04:25,721 It's a great read. 63 00:04:27,800 --> 00:04:32,302 Over the past ten years, there have been 40 DevOpsDays events in 21 countries, and it 64 00:04:32,302 --> 00:04:33,990 is growing. 65 00:04:33,990 --> 00:04:38,970 Patrick Debois was the lead for DevOpsDays from its inception in 2009 until 2015 and 66 00:04:38,970 --> 00:04:41,990 then Bridget Kromhout became the lead in 2015. 67 00:04:41,990 --> 00:04:46,030 She is also the co-host on the very popular podcast, Arrested DevOps. 68 00:04:46,030 --> 00:04:47,490 If you don't listen to it, you should. 69 00:04:47,490 --> 00:04:50,050 I have learned a lot from listening to Bridget. 70 00:04:50,050 --> 00:04:52,389 She is heavily involved with the DevOps community. 71 00:04:52,389 --> 00:04:55,900 She stepped down in 2020 but stayed on the advisory board of 72 00:04:55,900 --> 00:04:57,770 DevOpsDays. It is a great event. 73 00:04:57,770 --> 00:05:02,479 I got to attend DevOpsDays in New York City in March of 2020, and I loved every minute 74 00:05:02,479 --> 00:05:04,232 of it. 75 00:05:04,232 --> 00:05:09,750 These are some of the major influential people in the early DevOps movement: Patrick Debois, 76 00:05:09,750 --> 00:05:14,170 Andrew Clay Shaffer, John Allspaw, Jez Humble, Gene Kim, John Willis, Bridget Kromhout, and 77 00:05:14,170 --> 00:05:15,690 Nicole Forsgren. 78 00:05:15,690 --> 00:05:19,379 They weren’t the only ones but they went out and made a difference. 79 00:05:19,379 --> 00:05:21,919 They showed us how DevOps can be impactful. 80 00:05:21,919 --> 00:05:26,780 They explained that it is all about changing culture, not just about tools. 81 00:05:26,780 --> 00:05:30,530 They explored measurements and the idea of changing how you work. 82 00:05:30,530 --> 00:05:34,030 These are the early pioneers. 83 00:05:34,030 --> 00:05:35,360 Why is the history important? 84 00:05:35,360 --> 00:05:41,740 It is important because DevOps was a grassroots effort started by people like Patrick Debois, 85 00:05:41,740 --> 00:05:46,770 who just wanted to eliminate the roadblocks in software delivery and figure out how can 86 00:05:46,770 --> 00:05:50,050 development and operations work better together. 87 00:05:50,050 --> 00:05:56,410 Damon Edwards, who co-hosted a podcast with John Willis called the 'DevOps Cafe', said 88 00:05:56,410 --> 00:06:01,440 it best in his talk on “The (Short) History of DevOps” way back in 2012. 89 00:06:01,440 --> 00:06:05,520 DevOps is from the practitioners, by practitioners. 90 00:06:05,520 --> 00:06:08,960 It’s not a product, a specification, or job title. 91 00:06:08,960 --> 00:06:15,110 It is an experience-based movement, that is decentralized and open to all. 92 00:06:15,110 --> 00:06:20,379 People were beginning to realize that DevOps was a better way to work. 93 00:06:20,379 --> 00:06:24,210 In this video, you learned that: Patrick Debois started the DevOps movement 94 00:06:24,210 --> 00:06:29,539 in 2007 with a simple idea of getting development and operations to work better together. 95 00:06:29,539 --> 00:06:37,229 DevOps grew through the efforts of influential people such as Patrick Debois, Andrew Shafer, John Allspaw, 96 00:06:37,229 --> 00:06:42,319 Nicole Forsgren, Bridget Kromhout, Jez Humble, Gene Kim, and John Willis.