1 00:00:07,710 --> 00:00:12,450 After watching this video, you will be able to recognize the benefits of working DevOps, 2 00:00:12,450 --> 00:00:16,020 describe how Taylorism is not beneficial for software development, and 3 00:00:16,020 --> 00:00:20,020 recognize that software development is more like craftwork than factory work. 4 00:00:20,020 --> 00:00:22,930 In order to change your culture, you must 5 00:00:22,930 --> 00:00:25,390 change the way that people work. 6 00:00:25,390 --> 00:00:29,300 Working DevOps is all about facilitating a culture of teaming and collaboration. 7 00:00:29,300 --> 00:00:31,740 This is right from the Agile Manifesto. 8 00:00:31,740 --> 00:00:35,980 We value individuals and interactions over process and tools. 9 00:00:35,980 --> 00:00:40,350 Establishing Agile development as a shared discipline is at the core of building a strong 10 00:00:40,350 --> 00:00:42,399 DevOps culture. 11 00:00:42,399 --> 00:00:47,010 You also want to automate relentlessly to enable rapid DevOps responses. 12 00:00:47,010 --> 00:00:50,579 Sometimes automation is all people think about when they think about DevOps. 13 00:00:50,579 --> 00:00:56,499 DevOps is not just about automation but in order to respond rapidly, you must automate. 14 00:00:56,499 --> 00:01:02,059 Building a culture in which doing tasks manually is frowned upon, and automating task is rewarded 15 00:01:02,059 --> 00:01:04,839 is the culture you want to have. 16 00:01:04,839 --> 00:01:09,070 Pushing smaller releases faster, so that you can measure and remediate impact, is also 17 00:01:09,070 --> 00:01:10,700 extremely important. 18 00:01:10,700 --> 00:01:15,840 We want fast feedback loops and one way to achieve that is with frequent, smaller releases. 19 00:01:15,840 --> 00:01:19,740 This minimizes risk and maximizes learning. 20 00:01:19,740 --> 00:01:23,750 The problem we are up against here is that we have been working the same way since the industrial 21 00:01:23,750 --> 00:01:24,521 revolution. 22 00:01:24,521 --> 00:01:26,620 This is known as Taylorism. 23 00:01:26,620 --> 00:01:30,520 Taylorism is named after a U.S. industrial engineer, Frederick Winslow Taylor. 24 00:01:30,520 --> 00:01:35,560 In his 1911 book, Principles of Scientific Management, Taylor laid down the fundamental 25 00:01:35,560 --> 00:01:40,219 principles of large-scale manufacturing through assembly-line factories. 26 00:01:40,219 --> 00:01:45,820 During the industrial revolution, Taylor established the adoption of command-and-control management, 27 00:01:45,820 --> 00:01:51,189 which has become the dominant method of management in the Western world. 28 00:01:51,189 --> 00:01:56,860 He also prescribed that organizations be divided into independent functional silos. 29 00:01:56,860 --> 00:02:00,600 Taylor watched how workers executed their jobs and realized that if workers were separated 30 00:02:00,600 --> 00:02:04,579 into task-specific roles they could gain greater efficiency. 31 00:02:04,579 --> 00:02:07,479 This assembly line concept grew from this. 32 00:02:07,479 --> 00:02:11,510 For example, workers would just put on the doors of the cars and the next worker would 33 00:02:11,510 --> 00:02:15,110 just put on the windows and so on down the line. 34 00:02:15,110 --> 00:02:19,190 This was faster than one worker tooling up to put on a door, then retooling to put on 35 00:02:19,190 --> 00:02:22,250 a window and then tooling up for each stage of the assembly. 36 00:02:22,250 --> 00:02:28,210 One of the impacts of Taylorism that we see in business today is this idea of decision-making 37 00:02:28,210 --> 00:02:29,400 separated from work. 38 00:02:29,400 --> 00:02:33,110 In other words, managers do all the planning and decide what the worker should do, then the 39 00:02:33,110 --> 00:02:34,960 workers mindlessly do the tasks. 40 00:02:34,960 --> 00:02:36,690 They are told what to do. 41 00:02:36,690 --> 00:02:39,890 Many projects are still managed this way today. 42 00:02:39,890 --> 00:02:44,040 You can see the impact of Taylorism on information technology today. 43 00:02:44,040 --> 00:02:48,410 We have project management that is at the top of the command-and-control food chain. 44 00:02:48,410 --> 00:02:53,200 Project managers give the directions, architects design the systems, and handoff to the developers 45 00:02:53,200 --> 00:02:54,560 to code. 46 00:02:54,560 --> 00:02:56,330 Developers hand off to testers. 47 00:02:56,330 --> 00:02:58,520 Testers hand off to operations. 48 00:02:58,520 --> 00:03:00,520 Operations hands off to security. 49 00:03:00,520 --> 00:03:06,640 Each performs a task-specific role in their own silo with each handoff being an opportunity 50 00:03:06,640 --> 00:03:10,580 to make mistakes, lose context, or cause bottlenecks. 51 00:03:10,580 --> 00:03:14,780 Optimized roles may work well for making cars on an assembly line. 52 00:03:14,780 --> 00:03:18,560 It does not work well for software development. 53 00:03:18,560 --> 00:03:21,930 Automobiles are made up of standard parts. 54 00:03:21,930 --> 00:03:25,510 In software development, most of the parts don't even exist yet. 55 00:03:25,510 --> 00:03:27,790 If they did, we would buy them off the shelf. 56 00:03:27,790 --> 00:03:33,200 The fact that we have to write the code ourselves illustrates that this is bespoke, that is, customized 57 00:03:33,200 --> 00:03:35,174 or specialized. 58 00:03:35,174 --> 00:03:37,420 Software development is considered "knowledge work.” 59 00:03:37,420 --> 00:03:39,841 It is also "craftwork" when you think about it. 60 00:03:39,841 --> 00:03:44,540 It is creating a one-of-a-kind application that doesn't exist yet. 61 00:03:44,540 --> 00:03:48,820 When making automobiles, you tool up to make hundreds of thousands of them. 62 00:03:48,820 --> 00:03:51,670 That makes the rigor of tooling worthwhile. 63 00:03:51,670 --> 00:03:54,870 In software development, you are making one application. 64 00:03:54,870 --> 00:03:59,230 Why would you tool up an entire assembly line to make one of something? 65 00:03:59,230 --> 00:04:04,980 It doesn't make sense to treat software development like a factory assembly line. 66 00:04:04,980 --> 00:04:09,790 Steve Jobs once said, "It doesn't make sense to hire smart people and then tell them what to 67 00:04:09,790 --> 00:04:14,460 do; we hire smart people so they can tell us what to do." 68 00:04:14,460 --> 00:04:17,980 Managers need to be able to trust that they have hired the right people, let them know 69 00:04:17,980 --> 00:04:23,000 what needs to be done, and then get out of their way and let people amaze them. 70 00:04:23,000 --> 00:04:28,270 To fully work DevOps, you must abandon command and control management. 71 00:04:28,270 --> 00:04:29,630 Abandon Taylorism! 72 00:04:29,630 --> 00:04:35,889 To be DevOps, teams must stop working in silos and work together with a common goal. 73 00:04:35,889 --> 00:04:41,310 All of the hand-offs that silos cause will only slow them down. 74 00:04:41,310 --> 00:04:45,650 In this video, you learned that working DevOps means pushing small releases faster in order 75 00:04:45,650 --> 00:04:50,129 to gain feedback, minimize risk, and maximize learning. 76 00:04:50,129 --> 00:04:55,955 Taylorism was designed for factory work, while software development is like craftwork. 77 00:04:55,955 --> 00:05:02,209 Handoffs created by working in silos results in mistakes, bottlenecks, and delays.