1 00:00:06,833 --> 00:00:10,980 - Welcome to 7.4 Focus on Essential SAFe practices. 2 00:00:10,980 --> 00:00:13,385 In the last lesson, we talked about 3 00:00:13,385 --> 00:00:17,689 the top of the LPM pyramid, Strategy and Investment Funding. 4 00:00:17,689 --> 00:00:19,306 And we talked about how we connect 5 00:00:19,306 --> 00:00:20,954 the portfolio to enterprise strategy. 6 00:00:20,954 --> 00:00:23,286 We spent a fair amount of time on 7 00:00:23,286 --> 00:00:25,575 implementing lean agile budgeting and 8 00:00:25,575 --> 00:00:27,383 portfolio flow because we needed to show 9 00:00:27,383 --> 00:00:29,386 how it is that we can connect our work, 10 00:00:29,386 --> 00:00:30,935 our work in the trenches, the work that 11 00:00:30,935 --> 00:00:33,359 the developers and testers do everyday 12 00:00:33,359 --> 00:00:35,836 to the enterprise strategy how we can do that 13 00:00:35,836 --> 00:00:38,143 while minimizing cost accounting and friction 14 00:00:38,143 --> 00:00:40,044 and overhead associated with traditional 15 00:00:40,044 --> 00:00:43,103 project cost and establishing the flow of value. 16 00:00:43,103 --> 00:00:44,816 Now we're going to move to the second 17 00:00:44,816 --> 00:00:47,563 element on the pyramid, Agile Program Guidance. 18 00:00:47,563 --> 00:00:49,516 And here we're going to describe three different things. 19 00:00:49,516 --> 00:00:51,607 We're going to describe how we can focus 20 00:00:51,607 --> 00:00:55,167 on essential SAFe practices, support the agile PMO 21 00:00:55,167 --> 00:00:58,367 and comedial practices and sustain and improve. 22 00:00:58,367 --> 00:01:00,962 So LPM has a function here, it's not the traditional 23 00:01:00,962 --> 00:01:02,516 program management function, necessarily, 24 00:01:02,516 --> 00:01:04,874 we may have some aspects of that, but they have 25 00:01:04,874 --> 00:01:07,485 an important function in providing the context 26 00:01:07,485 --> 00:01:10,665 the business organization technical and financial 27 00:01:10,665 --> 00:01:13,483 context were by the arts can successfully thrive 28 00:01:13,483 --> 00:01:14,738 and deliver value. 29 00:01:14,738 --> 00:01:18,567 The first of these is to focus on essential SAFe practices. 30 00:01:18,567 --> 00:01:20,089 And the 10 essential SAFe practices 31 00:01:20,089 --> 00:01:22,653 have come from experience. 32 00:01:22,653 --> 00:01:24,150 As I mentioned earlier, very early on 33 00:01:24,150 --> 00:01:25,723 I showed the big picture and I said, 34 00:01:25,723 --> 00:01:27,790 Ah, we agree, there's a lot of stuff there. 35 00:01:27,790 --> 00:01:30,011 Building complex systems requires more than 36 00:01:30,011 --> 00:01:32,083 one thought, more than a couple different thoughts. 37 00:01:32,083 --> 00:01:34,412 More than just two or three activities. 38 00:01:34,412 --> 00:01:36,288 But essential SAFe is the simplest thing 39 00:01:36,288 --> 00:01:37,637 that can possibly work, it's the 40 00:01:37,637 --> 00:01:40,003 simplest SAFe you can deploy to support 100 41 00:01:40,003 --> 00:01:41,963 or a couple of hundred people building a value 42 00:01:41,963 --> 00:01:43,983 for solutions of a type. 43 00:01:43,983 --> 00:01:46,115 And the 10 essential elements that we've 44 00:01:46,115 --> 00:01:48,291 discovered by going back through various 45 00:01:48,291 --> 00:01:51,541 retrospectives and then also doing assessments 46 00:01:51,541 --> 00:01:55,402 and reassessing programs in flight, are these. 47 00:01:55,402 --> 00:01:57,222 Now we've covered most of them so I don't 48 00:01:57,222 --> 00:01:59,147 need to go into them in depth here, and I won't. 49 00:01:59,147 --> 00:02:01,795 But I do want to describe them briefly. 50 00:02:01,795 --> 00:02:04,887 Number 1 it is essential that we do understand 51 00:02:04,887 --> 00:02:07,759 lean-agile principles, can't ignore that. 52 00:02:07,759 --> 00:02:09,548 I said earlier, that that's probably the most 53 00:02:09,548 --> 00:02:11,685 important lesson I believe it today. 54 00:02:11,685 --> 00:02:13,332 I think everyday it reinforces the fact 55 00:02:13,332 --> 00:02:15,261 that if we get that right we're good. 56 00:02:15,261 --> 00:02:17,341 We need real agile teams and trains. 57 00:02:17,341 --> 00:02:19,269 What's that mean, Dean, you've already 58 00:02:19,269 --> 00:02:20,571 described teams and trains. 59 00:02:20,571 --> 00:02:23,403 Yeah, but I mean real agile teams and trains. 60 00:02:23,403 --> 00:02:24,634 Let me give you an example, 61 00:02:24,634 --> 00:02:28,708 I ran into a scrum team of requirements analysts. 62 00:02:28,708 --> 00:02:33,162 It's not funny, it's not an agile team, okay, 63 00:02:33,162 --> 00:02:34,876 but it was somebody's interpretation of 64 00:02:34,876 --> 00:02:37,082 what it means to be agile and be scrum. 65 00:02:37,082 --> 00:02:39,323 I worked in an organization that's a highly 66 00:02:39,323 --> 00:02:42,131 technical organization, very component based 67 00:02:42,131 --> 00:02:44,563 because they're building systems built on components. 68 00:02:44,563 --> 00:02:46,457 You can't wave your hand and smack 'em and say 69 00:02:46,457 --> 00:02:48,603 don't be component based, well you tell me 70 00:02:48,603 --> 00:02:50,415 what that thing is, that's got software in it 71 00:02:50,415 --> 00:02:52,577 and there's software over there in this other thing, 72 00:02:52,577 --> 00:02:55,783 so yeah, it's true that value flows through 73 00:02:55,783 --> 00:02:57,443 those things but we have to make this component 74 00:02:57,443 --> 00:02:59,119 work or nothing is going to happen. 75 00:02:59,119 --> 00:03:02,443 And we looked at their teams and didn't think 76 00:03:02,443 --> 00:03:04,278 that the flow was right, didn't seem like 77 00:03:04,278 --> 00:03:06,114 they were getting the right through put. 78 00:03:06,114 --> 00:03:07,514 So we asked further questions, and we said 79 00:03:07,514 --> 00:03:09,263 but what's that team, tell me about that team. 80 00:03:09,263 --> 00:03:12,012 Well, that's a team of developers, wow 81 00:03:12,012 --> 00:03:13,559 I think I'm hearing the same thing again. 82 00:03:13,559 --> 00:03:14,506 What's that other team? 83 00:03:14,506 --> 00:03:17,256 Well that team tests their stuff. 84 00:03:18,850 --> 00:03:21,723 Wow, those are not cross functional teams. 85 00:03:21,723 --> 00:03:24,539 So right there, at the get go, it's like, Hmm 86 00:03:24,539 --> 00:03:26,402 I don't think we've got this organized right 87 00:03:26,402 --> 00:03:28,160 and there saying, well, we've got expertise 88 00:03:28,160 --> 00:03:29,930 in test and expertise in development 89 00:03:29,930 --> 00:03:31,635 well let's put the people with expertise in test 90 00:03:31,635 --> 00:03:34,442 and expertise in development in the same team. 91 00:03:34,442 --> 00:03:35,783 Well that might make a larger team. 92 00:03:35,783 --> 00:03:37,811 Yeah, it might, maybe the team's too big 93 00:03:37,811 --> 00:03:38,874 we'll split it some other way. 94 00:03:38,874 --> 00:03:41,314 But we're not going to split it on functional lines. 95 00:03:41,314 --> 00:03:44,194 Real agile teams and real agile trains are necessary. 96 00:03:44,194 --> 00:03:47,337 I talked at length about cadence and synchronization. 97 00:03:47,337 --> 00:03:50,034 I talked about PI planning, not optional. 98 00:03:50,034 --> 00:03:52,587 I talked about DevOps and releasability 99 00:03:52,587 --> 00:03:54,954 and now I've wrapped that back into the larger story 100 00:03:54,954 --> 00:03:57,632 of basic lean startup mode and how it is 101 00:03:57,632 --> 00:03:59,234 we need to take a small batch and get it 102 00:03:59,234 --> 00:04:00,455 all the way through the system as quickly 103 00:04:00,455 --> 00:04:02,123 as possible, you need to do that. 104 00:04:02,123 --> 00:04:03,787 Now, it doesn't mean that you have 105 00:04:03,787 --> 00:04:06,183 to have completely functional DevOps 106 00:04:06,183 --> 00:04:07,953 and a full CV pipeline tomorrow. 107 00:04:07,953 --> 00:04:10,183 It just means that you're going to start working on it. 108 00:04:10,183 --> 00:04:12,190 And it means that whatever isn't working now 109 00:04:12,190 --> 00:04:13,714 if you're really cycle is too slow, 110 00:04:13,714 --> 00:04:16,758 if it takes six weeks, if you can imagine that, 111 00:04:16,758 --> 00:04:19,806 to do a regression test on a big, fat application 112 00:04:19,806 --> 00:04:22,882 set, I've seen that, if it takes six weeks, okay. 113 00:04:22,882 --> 00:04:25,010 What's it take to get it to six days. 114 00:04:25,010 --> 00:04:26,570 What's it take to get it to six hours. 115 00:04:26,570 --> 00:04:28,930 Because you certainly don't have any DevOps 116 00:04:28,930 --> 00:04:31,930 capability until you automate much of that testing. 117 00:04:31,930 --> 00:04:34,068 I mentioned ahead of time that the system demo 118 00:04:34,068 --> 00:04:35,458 wasn't optional, it isn't. 119 00:04:35,458 --> 00:04:37,919 Because if you can't demo the system, it's not sprinting. 120 00:04:37,919 --> 00:04:40,093 And I've gone in to organizations that were doing 121 00:04:40,093 --> 00:04:42,115 pretty well with SAFe that didn't have 122 00:04:42,115 --> 00:04:44,090 effective system demo, has some compromised 123 00:04:44,090 --> 00:04:47,123 teams and trains and lots of ability to improve 124 00:04:47,123 --> 00:04:49,130 just by going back to first principles. 125 00:04:49,130 --> 00:04:50,770 And that's what essential SAFe is about, 126 00:04:50,770 --> 00:04:51,950 the first principles. 127 00:04:51,950 --> 00:04:54,581 Inspect and adapt, not optional. 128 00:04:54,581 --> 00:04:56,567 We do it every 10 to 12 weeks. 129 00:04:56,567 --> 00:04:58,427 We learn something every time. 130 00:04:58,427 --> 00:05:00,579 We've been working most recently on decision making. 131 00:05:00,579 --> 00:05:02,720 I think we're about there, I think we now have 132 00:05:02,720 --> 00:05:05,211 a set of guidelines where a team of a type 133 00:05:05,211 --> 00:05:07,602 or an organization of a type knows that they 134 00:05:07,602 --> 00:05:09,626 can make these types of decisions but 135 00:05:09,626 --> 00:05:11,850 certain other decisions need to be centralized. 136 00:05:11,850 --> 00:05:12,930 Well, we have to create the borders 137 00:05:12,930 --> 00:05:14,355 and the boundaries for that. 138 00:05:14,355 --> 00:05:16,283 So the people really know how to behave. 139 00:05:16,283 --> 00:05:19,018 The IP iteration, we talked amongst ourselves. 140 00:05:19,018 --> 00:05:21,490 Maybe we have nine things, maybe it isn't essential. 141 00:05:21,490 --> 00:05:23,386 I think it is, cause if you don't have time 142 00:05:23,386 --> 00:05:24,666 for planning you won't take it. 143 00:05:24,666 --> 00:05:26,244 If you don't have time for inspect 144 00:05:26,244 --> 00:05:27,586 and adapt you won't take it. 145 00:05:27,586 --> 00:05:28,717 If you don't have time for ongoing training 146 00:05:28,717 --> 00:05:30,666 you won't take the ongoing training. 147 00:05:30,666 --> 00:05:32,691 Architectural runway, talked about that. 148 00:05:32,691 --> 00:05:34,099 Haven't yet talked about this, 149 00:05:34,099 --> 00:05:36,083 so trust me we absolutely will. 150 00:05:36,083 --> 00:05:38,370 Those are the 10 essential elements. 151 00:05:38,370 --> 00:05:41,620 Now, when you do that, well, you've already learned them. 152 00:05:41,620 --> 00:05:42,734 You've studied them somewhat. 153 00:05:42,734 --> 00:05:44,429 You can read about each of these things on the web. 154 00:05:44,429 --> 00:05:46,052 But you can also go to the site, 155 00:05:46,052 --> 00:05:49,247 go to scaledagileframework.com/essential-safe 156 00:05:49,247 --> 00:05:52,078 and you can download an assessment deck 157 00:05:52,078 --> 00:05:53,804 and that consists of a couple things. 158 00:05:53,804 --> 00:05:56,165 It consists of a set of power point slides 159 00:05:56,165 --> 00:05:58,420 you can use to talk about the essentials. 160 00:05:58,420 --> 00:06:00,876 And a way to kind of put checks by the things 161 00:06:00,876 --> 00:06:03,716 that, the symptoms, the problems that you're having. 162 00:06:03,716 --> 00:06:06,160 And then you build that out, and you build your own 163 00:06:06,160 --> 00:06:09,324 print out chart of things to work on. 164 00:06:09,324 --> 00:06:11,821 This team has some things to work on in this area. 165 00:06:11,821 --> 00:06:13,510 So this is a powerful tool that will help 166 00:06:13,510 --> 00:06:16,282 you understand how you're implementation is going. 167 00:06:16,282 --> 00:06:18,557 And also how to get started. 168 00:06:18,557 --> 00:06:21,766 So it isn't just a matter of, gosh, I'm running now 169 00:06:21,766 --> 00:06:23,299 I need these essentials, we're going to need 170 00:06:23,299 --> 00:06:26,284 to do these things well even for the first arc. 171 00:06:26,284 --> 00:06:27,698 So that's what essential SAFe is. 172 00:06:27,698 --> 00:06:30,188 It's a powerful tool in your toolkit. 173 00:06:30,188 --> 00:06:32,395 It's available online, it's available for free. 174 00:06:32,395 --> 00:06:35,917 Feel free to use it, download the toolkit. 175 00:06:35,917 --> 00:06:38,149 Do the assessment and pick what you think you need 176 00:06:38,149 --> 00:06:40,623 to work on next to improve your through put.