1 00:00:06,912 --> 00:00:08,576 - So now I'd like to introduce the basic 2 00:00:08,576 --> 00:00:11,529 constructs of the Scaled Agile Framework. 3 00:00:11,529 --> 00:00:12,868 What is SAFe? 4 00:00:12,868 --> 00:00:14,368 Well we like to think of it as knowledge 5 00:00:14,368 --> 00:00:16,272 for people building the world's most important systems, 6 00:00:16,272 --> 00:00:18,972 big systems, cyber-physical systems, satellites, 7 00:00:18,972 --> 00:00:22,168 medical devices, large scale software applications, 8 00:00:22,168 --> 00:00:24,972 CRM systems, the type of systems used everyday, 9 00:00:24,972 --> 00:00:27,808 mission critical systems, systems, banking, 10 00:00:27,808 --> 00:00:30,732 financial services, places where were a failure 11 00:00:30,732 --> 00:00:34,344 of a system is as unacceptable economic consequences. 12 00:00:34,344 --> 00:00:36,552 In order to do that, we've had to scale Agile 13 00:00:36,552 --> 00:00:40,135 to the full program and portfolio level. 14 00:00:40,135 --> 00:00:40,968 What is SAFe? 15 00:00:40,968 --> 00:00:42,372 It's a freely built knowledge base 16 00:00:42,372 --> 00:00:43,793 of integrated, proven patterns for enterprise 17 00:00:43,793 --> 00:00:45,476 Lean-Agile development. 18 00:00:45,476 --> 00:00:46,838 We've learned things in the field. 19 00:00:46,838 --> 00:00:48,550 We've applied Agile at the team level. 20 00:00:48,550 --> 00:00:50,020 We've applied Agile at the program level. 21 00:00:50,020 --> 00:00:52,228 We've applied Agile throughout the enterprise, 22 00:00:52,228 --> 00:00:53,620 and what we've learned we've recorded, 23 00:00:53,620 --> 00:00:56,260 tried to make it available and in an interactive 24 00:00:56,260 --> 00:00:58,556 knowledge base that you can use and learn from every day, 25 00:00:58,556 --> 00:01:00,628 and you can do that for free, there's no pay wall 26 00:01:00,628 --> 00:01:02,488 involved to get to SAFe. 27 00:01:02,488 --> 00:01:03,988 Here's a basic look at the big picture of SAFe. 28 00:01:03,988 --> 00:01:05,695 This is the full view. 29 00:01:05,695 --> 00:01:07,644 We'll show you narrower views later, 30 00:01:07,644 --> 00:01:09,428 or different slices and different perspectives 31 00:01:09,428 --> 00:01:10,524 on the framework. 32 00:01:10,524 --> 00:01:11,456 What do we believe in? 33 00:01:11,456 --> 00:01:13,692 We believe in things like built-in quality. 34 00:01:13,692 --> 00:01:16,329 It's not just a nice to have, it's a must to have. 35 00:01:16,329 --> 00:01:18,340 You can't go fast, the Lean Paradigm 36 00:01:18,340 --> 00:01:21,568 has a explicit understanding that every step 37 00:01:21,568 --> 00:01:23,832 of a process has to build quality in, 38 00:01:23,832 --> 00:01:25,870 because you have revisit steps you're gonna 39 00:01:25,870 --> 00:01:29,194 introduce massive delays and rework. 40 00:01:29,194 --> 00:01:31,376 If we can't execute large scale programs better, 41 00:01:31,376 --> 00:01:35,128 we can't build that satellite or that web service 42 00:01:35,128 --> 00:01:38,544 farm, or that application, quickly and effectively, 43 00:01:38,544 --> 00:01:40,692 we're not gonna have the trust of our stakeholders, 44 00:01:40,692 --> 00:01:42,656 we don't have the trust of our key stakeholders, 45 00:01:42,656 --> 00:01:45,028 that never works out very well for us. 46 00:01:45,028 --> 00:01:47,156 We get that in part by alignment. 47 00:01:47,156 --> 00:01:49,064 We simply all have to agree that we're building 48 00:01:49,064 --> 00:01:51,041 the same thing, it's not a matter of, 49 00:01:51,041 --> 00:01:53,744 so much of, management direction, it's a matter 50 00:01:53,744 --> 00:01:57,594 of management and the teams who build the systems 51 00:01:57,594 --> 00:01:59,592 coming to agree that we need to build 52 00:01:59,592 --> 00:02:01,373 this thing in this way. 53 00:02:01,373 --> 00:02:03,372 And that alignment is really valuable, 54 00:02:03,372 --> 00:02:06,072 is a really valuable commodity and a thing 55 00:02:06,072 --> 00:02:08,921 that we consistently strive to achieve and save. 56 00:02:08,921 --> 00:02:12,732 And transparency, what we wanna build in is trust, 57 00:02:12,732 --> 00:02:15,656 but we can't really program trust into a system. 58 00:02:15,656 --> 00:02:17,324 We can make a system transparent, 59 00:02:17,324 --> 00:02:21,448 so you can know, where you are at any point in time, 60 00:02:21,448 --> 00:02:24,416 and all facts are friendly, all the data is visible. 61 00:02:24,416 --> 00:02:25,990 You can make the right corrections 62 00:02:25,990 --> 00:02:29,216 as an individual practitioner, as a system architect, 63 00:02:29,216 --> 00:02:32,848 as somebody involved in the leadership role, 64 00:02:32,848 --> 00:02:34,811 you know what to do based upon the fact 65 00:02:34,811 --> 00:02:37,588 that you are in alignment, quality is being built in, 66 00:02:37,588 --> 00:02:39,808 and you have transparency in the process. 67 00:02:39,808 --> 00:02:42,056 So, you see a picture here, you see things, 68 00:02:42,056 --> 00:02:45,448 you see people for sure, you see various activities, 69 00:02:45,448 --> 00:02:46,992 you see things like P.I. planning, 70 00:02:46,992 --> 00:02:49,164 or maybe sprint planning, you see the roles 71 00:02:49,164 --> 00:02:51,372 of product owner etc., you see other constructs, 72 00:02:51,372 --> 00:02:53,212 you see features and you see user's stories, 73 00:02:53,212 --> 00:02:55,196 these are kind of common terms. 74 00:02:55,196 --> 00:02:56,934 Let's take a second and do a quick demo of SAFe 75 00:02:56,934 --> 00:02:58,947 so you can see how it's interactive, 76 00:02:58,947 --> 00:03:00,610 and give you a better understanding 77 00:03:00,610 --> 00:03:03,356 of what this knowledge base does for you. 78 00:03:03,356 --> 00:03:05,636 Okay, let's take a quick look at the SAFe website, 79 00:03:05,636 --> 00:03:08,008 and dive deep; I think we can get you a better 80 00:03:08,008 --> 00:03:09,596 understanding of how SAFe works by exercising it 81 00:03:09,596 --> 00:03:11,650 a little bit, and by talking 82 00:03:11,650 --> 00:03:13,361 about it with Powerpoint slides. 83 00:03:13,361 --> 00:03:14,788 We'll have plenty of time for that. 84 00:03:14,788 --> 00:03:16,676 So here we are, arrived at the Scaled Agile framework, 85 00:03:16,676 --> 00:03:20,084 ScaledAgileFramework.com, first thing's first. 86 00:03:20,084 --> 00:03:22,003 You might be working on our prior rev, 87 00:03:22,003 --> 00:03:24,672 and your enterprise may be involved in a 4.0 88 00:03:24,672 --> 00:03:27,192 transformation, so if you want to find SAFe 89 00:03:27,192 --> 00:03:29,144 4.0, click on SAFe 4.0, 90 00:03:29,144 --> 00:03:31,212 and this brings up the full site. 91 00:03:31,212 --> 00:03:33,190 It's still there, everything you're used 92 00:03:33,190 --> 00:03:35,112 to working with, looks like an old picture to me now, 93 00:03:35,112 --> 00:03:37,616 but a few months ago it seemed really fresh, 94 00:03:37,616 --> 00:03:39,025 and really new. 95 00:03:39,025 --> 00:03:40,844 Everything you're working for in 4.0 is there, 96 00:03:40,844 --> 00:03:42,521 but that's not the purpose of today. 97 00:03:42,521 --> 00:03:44,143 We're gonna talk about version 4.5, 98 00:03:44,143 --> 00:03:46,304 so if you're in the the middle of a SAFe 4.0 99 00:03:46,304 --> 00:03:48,464 rollout, you don't have to migrate 100 00:03:48,464 --> 00:03:50,816 to SAFe 4.5 immediately, we support not just the product 101 00:03:50,816 --> 00:03:52,707 and the framework, but all the course we're 102 00:03:52,707 --> 00:03:54,372 associated with version four. 103 00:03:54,372 --> 00:03:56,607 But I strongly encourage you to move, 104 00:03:56,607 --> 00:03:58,964 and this has been the last, almost two years 105 00:03:58,964 --> 00:04:01,585 driving innovations in Lean Startup, Lean UX, 106 00:04:01,585 --> 00:04:03,881 Dev Ops, and Continuous Delivery, 107 00:04:03,881 --> 00:04:05,908 Lean Portfolio Management, and other ways 108 00:04:05,908 --> 00:04:07,844 to think about helping large enterprises 109 00:04:07,844 --> 00:04:10,256 drive innovation as if they were smaller. 110 00:04:10,256 --> 00:04:12,776 So let's take a look at version 4.5. 111 00:04:12,776 --> 00:04:16,150 Now, this is a simpler view, and the reason is 112 00:04:16,150 --> 00:04:18,596 that I chose to display essential SAFe, 113 00:04:18,596 --> 00:04:20,308 so essential SAFe is right here, 114 00:04:20,308 --> 00:04:21,702 and we can navigate essential SAFe, 115 00:04:21,702 --> 00:04:23,756 we can work fully within that particular context, 116 00:04:23,756 --> 00:04:26,292 so if we wanna know something, maybe you were curious 117 00:04:26,292 --> 00:04:28,288 about, what's a business owner, 118 00:04:28,288 --> 00:04:29,684 that seems like a different kind 119 00:04:29,684 --> 00:04:30,568 of construct, who is that? 120 00:04:30,568 --> 00:04:33,764 We'll bring up an article on the business owner, 121 00:04:33,764 --> 00:04:36,252 typically with, hopefully an interesting quote. 122 00:04:36,252 --> 00:04:38,276 This particular one, "It's hard to imagine 123 00:04:38,276 --> 00:04:39,464 "a more stupid or more dangerous way 124 00:04:39,464 --> 00:04:40,948 "of making decisions, than by putting 125 00:04:40,948 --> 00:04:42,403 "those decisions in the hands of people 126 00:04:42,403 --> 00:04:44,532 "who pay no price for being wrong." 127 00:04:44,532 --> 00:04:46,904 We engage business owners in our Agile release 128 00:04:46,904 --> 00:04:48,988 training to make sure that's not the case. 129 00:04:48,988 --> 00:04:50,441 And you can read about business owners, 130 00:04:50,441 --> 00:04:53,036 what they do, if they're engaged in an activity 131 00:04:53,036 --> 00:04:55,256 like PI planning, or you could just click on PI planning 132 00:04:55,256 --> 00:04:57,610 and say what's PI planning, oh that's where 133 00:04:57,610 --> 00:05:00,252 we come together, and that's where the magic 134 00:05:00,252 --> 00:05:03,056 is and say if any talk about the PI planning function, 135 00:05:03,056 --> 00:05:04,964 but I don't want to lose my context, 136 00:05:04,964 --> 00:05:06,747 I was really wanting to learn more about business 137 00:05:06,747 --> 00:05:08,922 owners, so I'll read that full article. 138 00:05:08,922 --> 00:05:11,184 Gosh, I might want to read about Agile Release Trains, 139 00:05:11,184 --> 00:05:13,015 those are pretty powerful things. 140 00:05:13,015 --> 00:05:13,948 "The more alignment you have, 141 00:05:13,948 --> 00:05:15,404 "the more autonomy you can grant." 142 00:05:15,404 --> 00:05:16,736 That's kind of a cool quote. 143 00:05:16,736 --> 00:05:18,568 And we go on down to the specific responsibilities. 144 00:05:18,568 --> 00:05:21,508 All the roles are structured in such a way 145 00:05:21,508 --> 00:05:24,464 that each role highlights the specific 146 00:05:24,464 --> 00:05:26,232 responsibilities of the role. 147 00:05:26,232 --> 00:05:28,496 One way to look at SAFe is people do all the work, 148 00:05:28,496 --> 00:05:30,312 right, we're gonna talk about that real soon, 149 00:05:30,312 --> 00:05:32,188 it's a key principle of Lean. 150 00:05:32,188 --> 00:05:34,604 People do all the work, but what work do they do. 151 00:05:34,604 --> 00:05:38,128 And SAFe is in a sense, a set of responsibilities 152 00:05:38,128 --> 00:05:41,352 and they're aligned, and they work in such 153 00:05:41,352 --> 00:05:43,228 a way that they're interdependent, it's a system 154 00:05:43,228 --> 00:05:45,852 of responsibilities, so if the product manager 155 00:05:45,852 --> 00:05:47,908 does these functions, and the product owners 156 00:05:47,908 --> 00:05:49,552 do these functions, we'll have both kind of 157 00:05:49,552 --> 00:05:52,272 guidance at the program level, and the right 158 00:05:52,272 --> 00:05:54,536 detail that we need to execute at the team level. 159 00:05:54,536 --> 00:05:56,592 So that system responsibilities appears 160 00:05:56,592 --> 00:05:58,828 in all of those articles. 161 00:05:58,828 --> 00:06:00,508 And we'll talk a little bit about business value 162 00:06:00,508 --> 00:06:02,908 later, complex construct now, when we get to it 163 00:06:02,908 --> 00:06:04,904 it's gonna be fairly simple. 164 00:06:04,904 --> 00:06:06,672 That describes the set of responsibilities 165 00:06:06,672 --> 00:06:08,232 for that particular role. 166 00:06:08,232 --> 00:06:09,714 So we'll close that and say well what if 167 00:06:09,714 --> 00:06:10,872 we wanted to know something different, 168 00:06:10,872 --> 00:06:13,708 we wanted to learn about what is continuous exploration? 169 00:06:13,708 --> 00:06:16,304 We click on continuous exploration, 170 00:06:16,304 --> 00:06:18,552 and we come here to, in this case, 171 00:06:18,552 --> 00:06:21,292 a quote by Geoffrey Moore, the fuller pipeline 172 00:06:21,292 --> 00:06:23,921 of continuous exploration, continuous integration, 173 00:06:23,921 --> 00:06:26,968 continuous deployment, additional descriptions of that, 174 00:06:26,968 --> 00:06:30,042 and then details, further description of that process. 175 00:06:30,042 --> 00:06:32,084 We're gonna see this slide a little later 176 00:06:32,084 --> 00:06:34,484 when we talk about continuous exploration. 177 00:06:34,484 --> 00:06:37,030 Most articles have a few figures. 178 00:06:37,030 --> 00:06:38,804 Those figures typically are turn training. 179 00:06:38,804 --> 00:06:41,804 Lots of links, the first mention of any particular 180 00:06:41,804 --> 00:06:45,404 SAFe icon creates a link to that article. 181 00:06:45,404 --> 00:06:46,888 After that we don't bother because it just looks 182 00:06:46,888 --> 00:06:48,896 like too many links. 183 00:06:48,896 --> 00:06:51,103 Talk about the roles and responsibilities 184 00:06:51,103 --> 00:06:52,736 of collaboration, what happens there, 185 00:06:52,736 --> 00:06:56,366 how you build the vision roadmap and on like that. 186 00:06:56,366 --> 00:06:59,804 And then typically, you get to learn more 187 00:06:59,804 --> 00:07:01,316 at the end of every article, there're references to, 188 00:07:01,316 --> 00:07:04,064 I might wanna know about innovation games, 189 00:07:04,064 --> 00:07:05,605 that's a way to do ideation. 190 00:07:05,605 --> 00:07:07,392 I've written a lot about requirements, 191 00:07:07,392 --> 00:07:08,864 and requirements workshops, and basically 192 00:07:08,864 --> 00:07:13,004 processes to explore and elicit requirements from people. 193 00:07:13,004 --> 00:07:15,432 Lean Startup is a key part of our working, 194 00:07:15,432 --> 00:07:17,024 and other things, Gembawalks and Lean UX, 195 00:07:17,024 --> 00:07:18,896 all those references are there for you, 196 00:07:18,896 --> 00:07:21,268 so in your continuous learning journey 197 00:07:21,268 --> 00:07:22,604 that we'll describe later, there's lots 198 00:07:22,604 --> 00:07:23,981 of guidance for that. 199 00:07:23,981 --> 00:07:25,664 So let's step out of that, and talk about 200 00:07:25,664 --> 00:07:27,628 the configurability of SAFe, which was 201 00:07:27,628 --> 00:07:29,802 one of the main release themes of this. 202 00:07:29,802 --> 00:07:32,923 Prior to this, if you go to version four of SAFe, 203 00:07:32,923 --> 00:07:35,876 it is what it is, there's no way to configure it, right? 204 00:07:35,876 --> 00:07:37,828 I can expand and collapse one level, and that 205 00:07:37,828 --> 00:07:39,824 was kind of helpful, and that's our first step 206 00:07:39,824 --> 00:07:42,084 towards configurability, but it didn't give us 207 00:07:42,084 --> 00:07:43,856 kind of the full configurability that we need, 208 00:07:43,856 --> 00:07:46,194 so we don't wanna use that version anymore. 209 00:07:46,194 --> 00:07:47,684 That's kind of old and boring. 210 00:07:47,684 --> 00:07:48,808 We wanna go to the new version, 211 00:07:48,808 --> 00:07:52,016 and here I configure the exact view I need. 212 00:07:52,016 --> 00:07:53,532 In the introduction, we're gonna describe 213 00:07:53,532 --> 00:07:56,144 these configurations briefly, but essential SAFe 214 00:07:56,144 --> 00:07:58,616 is the simplest, we add the portfolio level 215 00:07:58,616 --> 00:08:00,088 to that, we have portfolio SAFe, one more click 216 00:08:00,088 --> 00:08:03,792 we get larger solution SAFe, which we'll explain 217 00:08:03,792 --> 00:08:06,176 in some detail in a later lesson, 218 00:08:06,176 --> 00:08:08,276 totally focused on that, and full SAFe 219 00:08:08,276 --> 00:08:10,964 is really the inclusion of all the above, 220 00:08:10,964 --> 00:08:13,392 so it's full SAFe, you have the full big picture 221 00:08:13,392 --> 00:08:15,268 that might be a lot to think about initially, 222 00:08:15,268 --> 00:08:18,284 I might wanna just start with two arts in a portfolio, 223 00:08:18,284 --> 00:08:21,208 I might be building a big solution, I don't care 224 00:08:21,208 --> 00:08:22,784 about the portfolio, essential SAFe is too small for me, 225 00:08:22,784 --> 00:08:26,924 and it gives you that full set of configurability items. 226 00:08:26,924 --> 00:08:29,144 When you bring up a view with a new configuration, 227 00:08:29,144 --> 00:08:31,332 new articles appear, things like solution context 228 00:08:31,332 --> 00:08:33,672 become important when you're building 229 00:08:33,672 --> 00:08:35,034 a really big system, as we'll talk about later, 230 00:08:35,034 --> 00:08:38,068 so context is the key from that comes 231 00:08:38,068 --> 00:08:39,655 the understanding of everything, 232 00:08:39,655 --> 00:08:41,204 and that's the article on solution context. 233 00:08:41,204 --> 00:08:43,404 So that gives you the basic idea 234 00:08:43,404 --> 00:08:45,416 of the navigation paradigm, a couple 235 00:08:45,416 --> 00:08:47,548 of other things, if you're familiar with SAFe 236 00:08:47,548 --> 00:08:49,692 and what's really is interesting to you 237 00:08:49,692 --> 00:08:51,644 is what's new, click on what's new in SAFe, 238 00:08:51,644 --> 00:08:55,812 and here's an article that Richard put together 239 00:08:55,812 --> 00:08:57,944 that's really good description of the things that are new, 240 00:08:57,944 --> 00:09:00,773 you can see things like essential SAFe 241 00:09:00,773 --> 00:09:03,086 and configurability, innovation with Lean Startup 242 00:09:03,086 --> 00:09:05,248 and Lean UX, Scalable DevOps and continuous delivery, 243 00:09:05,248 --> 00:09:07,692 the implementation roadmap, and a lot 244 00:09:07,692 --> 00:09:09,208 of other important stuff. 245 00:09:09,208 --> 00:09:10,853 This is a fairly long article cuz it has 246 00:09:10,853 --> 00:09:13,168 a lot to say, one of the things it has to say 247 00:09:13,168 --> 00:09:15,476 is we're still backwards compatible with version four. 248 00:09:15,476 --> 00:09:16,961 All the features you've done, you don't have 249 00:09:16,961 --> 00:09:18,552 to redo anything, you don't have to rework 250 00:09:18,552 --> 00:09:19,932 any history, you just can add the new features, 251 00:09:19,932 --> 00:09:23,529 as any good product solution does. 252 00:09:23,529 --> 00:09:25,168 A quick look at the configurations, 253 00:09:25,168 --> 00:09:27,748 you may wanna download posters. 254 00:09:27,748 --> 00:09:29,532 You may say, you know I'd like to put a picture 255 00:09:29,532 --> 00:09:31,348 on my wall of that thing, so we'll go here 256 00:09:31,348 --> 00:09:32,564 and we'll say what do I get? 257 00:09:32,564 --> 00:09:35,981 I'd like this download portfolio SAFe is pretty cool. 258 00:09:35,981 --> 00:09:38,168 Let me download that one, and away it goes 259 00:09:38,168 --> 00:09:39,732 into my folder, and I have a PDF of that 260 00:09:39,732 --> 00:09:41,908 I can print or use, or download any 261 00:09:41,908 --> 00:09:44,668 of the other configurations as well. 262 00:09:44,668 --> 00:09:47,216 Let's go back to the main menu here in SAFe, 263 00:09:47,216 --> 00:09:49,796 and talk about some of the things that surround SAFe. 264 00:09:49,796 --> 00:09:52,092 I'm gonna spend the whole course talking 265 00:09:52,092 --> 00:09:54,400 about these aspects of SAFe: activities, 266 00:09:54,400 --> 00:09:56,607 various artifacts, and various events. 267 00:09:56,607 --> 00:09:57,884 So we don't need to cover that now. 268 00:09:57,884 --> 00:09:59,304 You can go there at any time. 269 00:09:59,304 --> 00:10:01,916 You can click on what we call the spanning palate. 270 00:10:01,916 --> 00:10:04,872 Why is is span, because I could have a vision 271 00:10:04,872 --> 00:10:07,374 that, a team could have a vision, art could have a vision, 272 00:10:07,374 --> 00:10:08,936 portfolio or large solution. 273 00:10:08,936 --> 00:10:10,663 Those things are on the spanning palate 274 00:10:10,663 --> 00:10:11,968 cuz you can use them anywhere. 275 00:10:11,968 --> 00:10:15,268 I'll navigate from full SAFe and show you some other things. 276 00:10:15,268 --> 00:10:17,156 Of course, there's a set of menus at the top, 277 00:10:17,156 --> 00:10:19,496 there's some interesting things at the bottom as well. 278 00:10:19,496 --> 00:10:22,348 Is the blog, we constantly evolve SAFe. 279 00:10:22,348 --> 00:10:25,149 If you look at this article, this is a new blog article, 280 00:10:25,149 --> 00:10:27,416 that says there's new Lean Portfolio 281 00:10:27,416 --> 00:10:29,232 management article in SAFe. 282 00:10:29,232 --> 00:10:31,184 We don't change the big picture very often, 283 00:10:31,184 --> 00:10:33,536 maybe annually or so, but we're constantly 284 00:10:33,536 --> 00:10:35,496 creating new content, so we can do continuous delivery 285 00:10:35,496 --> 00:10:39,685 of content behind the scenes, so if we're not happy 286 00:10:39,685 --> 00:10:42,281 with the LPM article, it was PPM, and we didn't 287 00:10:42,281 --> 00:10:45,164 get it where we wanted, we can continue to work on that, 288 00:10:45,164 --> 00:10:47,323 but when we do, any change we make to SAFe will be blogged. 289 00:10:47,323 --> 00:10:51,490 So we'll assure you that we won't surprise you with things 290 00:10:52,772 --> 00:10:54,868 that are new and different that we don't give you 291 00:10:54,868 --> 00:10:58,952 a chance, in addition I'll tweet that, so @DeanLeffingwell, 292 00:10:58,952 --> 00:11:00,512 you can follow me if you like on Twitter, 293 00:11:00,512 --> 00:11:02,472 and I'll make sure that if there's a change to SAFe 294 00:11:02,472 --> 00:11:04,244 that you need to know about, that'll show up 295 00:11:04,244 --> 00:11:05,852 on your Twitter feed, so we're not gonna surprise you 296 00:11:05,852 --> 00:11:07,676 with some stuff behind the scenes, you're about 297 00:11:07,676 --> 00:11:10,632 to launch an initiative or do some training 298 00:11:10,632 --> 00:11:12,597 and find something new, so that's important, 299 00:11:12,597 --> 00:11:15,152 that's the blog, and we, the blog is fairly informal, 300 00:11:15,152 --> 00:11:17,700 it's easy for us to put up a blog post, 301 00:11:17,700 --> 00:11:21,016 the blog is also organized by category, 302 00:11:21,016 --> 00:11:23,312 so if you wanna find a particular category, 303 00:11:23,312 --> 00:11:25,816 you can search by category and find your way 304 00:11:25,816 --> 00:11:27,180 through the blog. 305 00:11:27,180 --> 00:11:28,484 So that's pretty helpful. 306 00:11:28,484 --> 00:11:30,344 Other particularly deep and rich environments, 307 00:11:30,344 --> 00:11:32,323 the implementation roadmap. 308 00:11:32,323 --> 00:11:34,184 We mentioned that very briefly. 309 00:11:34,184 --> 00:11:36,341 This is actually a series of articles 310 00:11:36,341 --> 00:11:40,091 so this particular article is itself a domain 311 00:11:41,132 --> 00:11:43,484 into itself and has multiple articles with it. 312 00:11:43,484 --> 00:11:45,840 This is the 12 stage implementation roadmap. 313 00:11:45,840 --> 00:11:48,164 We're not gonna go through that in this course. 314 00:11:48,164 --> 00:11:50,684 It's kind of a bridge too far, or too deep, 315 00:11:50,684 --> 00:11:52,232 but you can go and read about it, 316 00:11:52,232 --> 00:11:55,156 and say, hmm, I wonder how we would train teams 317 00:11:55,156 --> 00:11:57,180 and launch the ART, what's that look like, 318 00:11:57,180 --> 00:11:59,160 and click on that article just like any other article. 319 00:11:59,160 --> 00:12:01,360 More and more, there're what we call the subdomains, 320 00:12:01,360 --> 00:12:03,944 which is areas of interest that require additional 321 00:12:03,944 --> 00:12:07,080 content, and additional ways to reach that content, 322 00:12:07,080 --> 00:12:10,740 so not everything can appear on the big picture. 323 00:12:10,740 --> 00:12:12,872 So that's implementation roadmap. 324 00:12:12,872 --> 00:12:14,084 What else is important? 325 00:12:14,084 --> 00:12:15,452 Case studies are important. 326 00:12:15,452 --> 00:12:17,100 We love case studies. 327 00:12:17,100 --> 00:12:19,784 We don't write them, that's our customers' responsibility, 328 00:12:19,784 --> 00:12:22,260 so you see here case studies, consumer product 329 00:12:22,260 --> 00:12:24,676 companies like fitbit, Sony Entertainment, a 330 00:12:24,676 --> 00:12:27,164 big insurance company is Northwester Mutual, 331 00:12:27,164 --> 00:12:30,152 Intel, been with us for years, doing really good work, 332 00:12:30,152 --> 00:12:33,932 Philips, Kantar Retail, a Swiss company, Amdocs, 333 00:12:33,932 --> 00:12:37,156 an Israeli company, AstraZeneca, a Swiss company, 334 00:12:37,156 --> 00:12:39,932 Westpac, Australia's first bank, HP Enterprise, 335 00:12:39,932 --> 00:12:42,000 lots and lots of case studies. 336 00:12:42,000 --> 00:12:43,844 In addition to the case studies these are what 337 00:12:43,844 --> 00:12:46,680 we call stories or honorable mention. 338 00:12:46,680 --> 00:12:49,412 SAFe is being used extensively in the government now. 339 00:12:49,412 --> 00:12:51,644 It's being used in places like the patent 340 00:12:51,644 --> 00:12:54,000 and trademark office, this isn't a case study. 341 00:12:54,000 --> 00:12:56,324 This is the homeland security article talking 342 00:12:56,324 --> 00:12:58,336 about the fact that we've deployed SAFe 343 00:12:58,336 --> 00:13:00,360 in that particular context, in that particular environment. 344 00:13:00,360 --> 00:13:04,395 So the case studies are probably valuable for you, 345 00:13:04,395 --> 00:13:06,032 especially if you're in implementation. 346 00:13:06,032 --> 00:13:08,864 Other resources, let's take a look here 347 00:13:08,864 --> 00:13:10,768 at some interesting things. 348 00:13:10,768 --> 00:13:12,884 Books on SAFe, if you can imagine that we have those. 349 00:13:12,884 --> 00:13:14,699 You could download those posters, 350 00:13:14,699 --> 00:13:16,424 you could go to presentations and videos. 351 00:13:16,424 --> 00:13:18,690 You can see some cool stuff, you can see various 352 00:13:18,690 --> 00:13:22,857 videos of me, there's a really brief executive briefing. 353 00:13:24,092 --> 00:13:26,432 There's Enbar doing SAFe in five minutes, 354 00:13:26,432 --> 00:13:28,636 a bunch of recent interviews I just did some 355 00:13:28,636 --> 00:13:31,049 at Agile 2017, talking about three major topics: 356 00:13:31,049 --> 00:13:34,724 the future of SAFe, impediments to implementation, 357 00:13:34,724 --> 00:13:37,380 and the role of projects and project managers. 358 00:13:37,380 --> 00:13:39,213 What else is fun here? 359 00:13:40,710 --> 00:13:43,052 One interesting thing is it's not a trivial thing 360 00:13:43,052 --> 00:13:45,433 to understand SAFes, so if you go to resources, 361 00:13:45,433 --> 00:13:48,104 you're gonna find the glossary. 362 00:13:48,104 --> 00:13:50,144 And English may not be your first language, 363 00:13:50,144 --> 00:13:52,096 which we don't translate all of SAFe, however 364 00:13:52,096 --> 00:13:54,616 we provide very tight glossary elements, 365 00:13:54,616 --> 00:13:57,392 and these are actually compiled from the site itself. 366 00:13:57,392 --> 00:13:59,372 So this is not a separate project. 367 00:13:59,372 --> 00:14:01,336 This is one of our efforts for DevOps, 368 00:14:01,336 --> 00:14:03,160 to make sure that when we write a thing 369 00:14:03,160 --> 00:14:05,372 we only write it once, so the glossary item occurs 370 00:14:05,372 --> 00:14:07,844 in the article with tags, and then it's sucked 371 00:14:07,844 --> 00:14:10,528 into the glossary itself, so the glossary 372 00:14:10,528 --> 00:14:12,944 is always current, it always matches the articles. 373 00:14:12,944 --> 00:14:15,452 But if this is not your first language, 374 00:14:15,452 --> 00:14:18,136 maybe you wanna translate into your language 375 00:14:18,136 --> 00:14:20,056 so at least you have an idea of what these major items 376 00:14:20,056 --> 00:14:23,056 mean, so if you're a Hebrew speaker, 377 00:14:24,436 --> 00:14:27,032 we have a couple of those, interestingly enough. 378 00:14:27,032 --> 00:14:29,924 Translate to Hebrew, and you can read it in Hebrew. 379 00:14:29,924 --> 00:14:33,032 There're whole hosts here, these are Google Translate, 380 00:14:33,032 --> 00:14:35,192 so before we get too excited we need to recognize 381 00:14:35,192 --> 00:14:38,192 that this is Google Translate's best effort 382 00:14:38,192 --> 00:14:40,740 to translate into Dutch or whatever. 383 00:14:40,740 --> 00:14:42,897 And it's pretty good, and it's virtually impossible 384 00:14:42,897 --> 00:14:45,556 for us to compete with the velocity of that. 385 00:14:45,556 --> 00:14:48,164 So another another form of DevOps for us, 386 00:14:48,164 --> 00:14:50,684 another form of faster time to market 387 00:14:50,684 --> 00:14:53,912 and support multiple language users 388 00:14:53,912 --> 00:14:57,212 was to make sure that the glossary was tagged, 389 00:14:57,212 --> 00:14:59,804 to make sure that every article was uniform 390 00:14:59,804 --> 00:15:02,372 and had a glossary element, that was tagged. 391 00:15:02,372 --> 00:15:04,892 That those got pulled in to a specific page, 392 00:15:04,892 --> 00:15:06,464 and then they could be translated. 393 00:15:06,464 --> 00:15:07,800 So we don't do any manual translations 394 00:15:07,800 --> 00:15:10,424 of glossaries anymore, and we don't do any 395 00:15:10,424 --> 00:15:12,060 manual production production of the glossary. 396 00:15:12,060 --> 00:15:13,660 That's one of our steps toward DevOps, 397 00:15:13,660 --> 00:15:14,908 and more continuous delivery. 398 00:15:14,908 --> 00:15:17,564 I have to change it back to English cuz I can't 399 00:15:17,564 --> 00:15:19,172 navigate this thing in Dutch. 400 00:15:19,172 --> 00:15:20,100 Is there anything else? 401 00:15:20,100 --> 00:15:21,449 Well probably finally there is. 402 00:15:21,449 --> 00:15:23,372 You're gonna wanna know more about SAFe 403 00:15:23,372 --> 00:15:25,709 you're involved right now, in a training course, 404 00:15:25,709 --> 00:15:28,320 we offer additional courses, instructor led training, 405 00:15:28,320 --> 00:15:30,853 things like kind of the bread and butter course 406 00:15:30,853 --> 00:15:32,956 implementing SAFe, this is the four day course, 407 00:15:32,956 --> 00:15:35,264 this is the implementing SAFe course, this 408 00:15:35,264 --> 00:15:36,900 is the four day course for SPCs. 409 00:15:36,900 --> 00:15:40,754 SPCs are trained and authorized and licensed to teach 410 00:15:40,754 --> 00:15:42,540 things like leading SAFe and other courses. 411 00:15:42,540 --> 00:15:44,400 So the course I'm teaching you now 412 00:15:44,400 --> 00:15:46,979 is also taught by other SPCs. 413 00:15:46,979 --> 00:15:48,632 That's where you can go to find, 414 00:15:48,632 --> 00:15:51,195 get help, if you wanted to find out who 415 00:15:51,195 --> 00:15:52,952 is teaching implementing SAFe and you wanted 416 00:15:52,952 --> 00:15:56,535 to find out who that would be in Australia. 417 00:15:58,052 --> 00:16:01,969 And next, let's just say in October, and do go. 418 00:16:04,860 --> 00:16:07,304 We'll see if anybody's teaching that course in October. 419 00:16:07,304 --> 00:16:10,800 The answer is in Australia, no events to display. 420 00:16:10,800 --> 00:16:13,723 So belay that, let's go back, let's try something different. 421 00:16:13,723 --> 00:16:16,080 Let's go back to find training. 422 00:16:16,080 --> 00:16:17,997 Locate a class near me. 423 00:16:20,080 --> 00:16:22,228 Let's make it a little bit easier here. 424 00:16:22,228 --> 00:16:26,395 Let's filter by course, we wanna do implementing SAFe. 425 00:16:28,484 --> 00:16:31,651 We wanna do that in the United States. 426 00:16:33,932 --> 00:16:37,320 We do a search and see what we come up with, 427 00:16:37,320 --> 00:16:39,992 do a little bit of work and here, we have a class 428 00:16:39,992 --> 00:16:43,636 coming up in Houston August 29th, New York City, 429 00:16:43,636 --> 00:16:45,838 Reston, Virginia, more and more if you click 430 00:16:45,838 --> 00:16:48,420 on that class, you can register for that class right there. 431 00:16:48,420 --> 00:16:50,621 We try to make it easy for you to find the knowledge 432 00:16:50,621 --> 00:16:53,372 that you need to be successful with SAFe. 433 00:16:53,372 --> 00:16:56,802 That's it for the demo, let's get back to class. 434 00:16:56,802 --> 00:16:58,844 With that demo, you should have a pretty good understanding 435 00:16:58,844 --> 00:17:00,580 of the interactivity of SAFe, and you can pause this 436 00:17:00,580 --> 00:17:04,740 and go to SkilledAgileFramework.com, you don't need me 437 00:17:04,740 --> 00:17:06,734 to click around, that's we made it freely revealed 438 00:17:06,734 --> 00:17:09,616 and publicly facing, so feel free to browse 439 00:17:09,616 --> 00:17:11,836 and look at your favorite icon or whatever. 440 00:17:11,836 --> 00:17:13,798 A little bit about the history. 441 00:17:13,798 --> 00:17:15,316 On a relative basis, we haven't been at this 442 00:17:15,316 --> 00:17:17,040 too long, I mean, I don't know about you, 443 00:17:17,040 --> 00:17:20,159 but I don't know if 2011 seems like forever ago, 444 00:17:20,159 --> 00:17:21,420 or just last year. 445 00:17:21,420 --> 00:17:23,160 That was when we first released SAFe. 446 00:17:23,160 --> 00:17:25,257 We spent the prior years, five six years 447 00:17:25,257 --> 00:17:27,344 in the field, understanding what was working 448 00:17:27,344 --> 00:17:29,501 in applying Agile at Scale, and we evolved 449 00:17:29,501 --> 00:17:34,004 that through version 2.0, version three, which 450 00:17:34,004 --> 00:17:35,084 is certainly a seminal milestone. 451 00:17:35,084 --> 00:17:37,317 We made a quick branch, we did a big experiment 452 00:17:37,317 --> 00:17:39,752 off to the side with what we called 453 00:17:39,752 --> 00:17:41,776 SAFe for Lean Systems Engineering. 454 00:17:41,776 --> 00:17:43,980 We eventually collapsed that branch into SAFe 455 00:17:43,980 --> 00:17:45,540 because we realized that nobody wants to have 456 00:17:45,540 --> 00:17:46,980 two frameworks at work. 457 00:17:46,980 --> 00:17:48,736 If I'm building a satellite, and there's 458 00:17:48,736 --> 00:17:52,156 a ground station as a giant software, 459 00:17:52,156 --> 00:17:53,176 suite of software applications, it also has 460 00:17:53,176 --> 00:17:55,096 mechanical parts, well I still wanna talk 461 00:17:55,096 --> 00:17:56,492 about the same things. 462 00:17:56,492 --> 00:17:58,184 I wanna use the same basic processes as well. 463 00:17:58,184 --> 00:18:00,341 That brought us to version four, where we merged 464 00:18:00,341 --> 00:18:02,476 those two together. 465 00:18:02,476 --> 00:18:06,104 Version 4.0 was available until about, gosh, 466 00:18:06,104 --> 00:18:10,860 about July of this year, and then, now at version 4.5 467 00:18:10,860 --> 00:18:13,724 we'll spend time in this course teaching 468 00:18:13,724 --> 00:18:15,884 a pretty thorough introduction to 4.5. 469 00:18:15,884 --> 00:18:18,076 But what does this slide imply? 470 00:18:18,076 --> 00:18:20,100 Are you done, are we done? 471 00:18:20,100 --> 00:18:21,764 I don't think so. 472 00:18:21,764 --> 00:18:23,656 Together we're on a learning journey, 473 00:18:23,656 --> 00:18:25,412 we're learning new things every day, 474 00:18:25,412 --> 00:18:27,512 every time any of us goes into the field 475 00:18:27,512 --> 00:18:29,672 we learn something new, and we intend 476 00:18:29,672 --> 00:18:31,480 to continue to evolve SAFe. 477 00:18:31,480 --> 00:18:32,956 I like to make a joke in class sometimes, 478 00:18:32,956 --> 00:18:34,876 I really look forward to version eight, 479 00:18:34,876 --> 00:18:36,764 somebody in class said, well why don't you call 480 00:18:36,764 --> 00:18:38,264 this version version eight, and I said 481 00:18:38,264 --> 00:18:39,869 well that'd just be cheating. 482 00:18:39,869 --> 00:18:41,864 So we're on a path together, we will continue 483 00:18:41,864 --> 00:18:43,516 to learn, we'll continue to apply these bodies of knowledge, 484 00:18:43,516 --> 00:18:47,624 Agile development, and advances in that area, 485 00:18:47,624 --> 00:18:50,880 Lean product development, kinda a late breaking 486 00:18:50,880 --> 00:18:54,256 entry into understanding how to build big systems 487 00:18:54,256 --> 00:18:56,716 in a lean and more agile fashion, how to reduce 488 00:18:56,716 --> 00:18:59,908 the cost of delay, get time to market more quickly, 489 00:18:59,908 --> 00:19:04,075 and then this, somewhat old school of systems thinking, 490 00:19:04,980 --> 00:19:07,784 which is the system is greater than the sum of its parts, 491 00:19:07,784 --> 00:19:09,314 and a part can't even understand 492 00:19:09,314 --> 00:19:11,416 the full context of the system. 493 00:19:11,416 --> 00:19:13,516 We will apply all of those bodies of knowledge together, 494 00:19:13,516 --> 00:19:16,036 and we look forward to future versions. 495 00:19:16,036 --> 00:19:18,464 But for now, we've just released version 4.5, 496 00:19:18,464 --> 00:19:20,490 so let's dive in to that. 497 00:19:20,490 --> 00:19:22,620 I showed you a pretty big picture here, 498 00:19:22,620 --> 00:19:23,937 and maybe it was a little bit intimidating 499 00:19:23,937 --> 00:19:26,624 with all these icons and things flying around the screen, 500 00:19:26,624 --> 00:19:28,216 well they're not flying around, you saw them 501 00:19:28,216 --> 00:19:29,861 fly around when we did the demo, 502 00:19:29,861 --> 00:19:33,032 do you need all of that stuff, that's a fair question. 503 00:19:33,032 --> 00:19:34,396 There's a lot of things there, and I've had 504 00:19:34,396 --> 00:19:38,624 some very bright people, and some very capable CIOs 505 00:19:38,624 --> 00:19:40,724 and VPs of technology come to me and look at SAFe 506 00:19:40,724 --> 00:19:43,292 and say, I'm not sure we can do all that Dean, 507 00:19:43,292 --> 00:19:45,882 we don't argue that we wanna have a better 508 00:19:45,882 --> 00:19:47,340 flow of value through the portfolio, 509 00:19:47,340 --> 00:19:49,980 and we kinda have a rough understanding of Lean budgets. 510 00:19:49,980 --> 00:19:52,304 Do we have to do all of that to succeed? 511 00:19:52,304 --> 00:19:54,676 Well the good news is, no you don't. 512 00:19:54,676 --> 00:19:56,852 And in this version, 4.5 of SAFe, 513 00:19:56,852 --> 00:19:58,900 we're introducing configurability. 514 00:19:58,900 --> 00:20:01,456 The first element of that is essential SAFe, 515 00:20:01,456 --> 00:20:04,860 and that provides the fundamental foundation for success. 516 00:20:04,860 --> 00:20:06,840 I won't go through it in much detail now 517 00:20:06,840 --> 00:20:08,716 because we'll definitely go through these 518 00:20:08,716 --> 00:20:11,356 roles and activities and artifacts, 519 00:20:11,356 --> 00:20:13,876 the things you build as you build systems, 520 00:20:13,876 --> 00:20:16,979 but it is the basic foundational element. 521 00:20:16,979 --> 00:20:19,680 It consists of certain roles, and certain activities. 522 00:20:19,680 --> 00:20:22,649 Things you do, it supports the continuous release 523 00:20:22,649 --> 00:20:25,052 of value through the continuous delivery pipeline. 524 00:20:25,052 --> 00:20:29,440 It describes the DevOps culture, automation, 525 00:20:29,440 --> 00:20:31,168 lean flow, measurement, and recovery, 526 00:20:31,168 --> 00:20:33,180 and it has all the activities we need to build 527 00:20:33,180 --> 00:20:35,476 a big system, and that's this thing here. 528 00:20:35,476 --> 00:20:37,424 That's the solution we're gonna build together. 529 00:20:37,424 --> 00:20:39,460 It combines teams of teams working together 530 00:20:39,460 --> 00:20:41,984 to achieve that, that's essential SAFe. 531 00:20:41,984 --> 00:20:44,895 Again, we'll have lots of time to talk about that further. 532 00:20:44,895 --> 00:20:47,354 Essential SAFe is built on Agile teams, why? 533 00:20:47,354 --> 00:20:49,964 Because nothing beats and Agile team. 534 00:20:49,964 --> 00:20:53,430 I'm on an Agile team, when I teach this class live, 535 00:20:53,430 --> 00:20:55,541 I always ask people, how many people here 536 00:20:55,541 --> 00:20:57,644 are on an Agile team, and typically only about two thirds 537 00:20:57,644 --> 00:20:59,972 raise their hand, maybe half, and I say, 538 00:20:59,972 --> 00:21:03,736 how many wanna go back to not being part of an Agile team? 539 00:21:03,736 --> 00:21:06,236 And nobody raises their hands. 540 00:21:08,220 --> 00:21:10,532 It's just more fun, it's more dynamic, 541 00:21:10,532 --> 00:21:12,284 it's faster, it's quicker, it's more responsive, 542 00:21:12,284 --> 00:21:15,676 being part of a team that achieves value is great. 543 00:21:15,676 --> 00:21:17,700 What are these teams? 544 00:21:17,700 --> 00:21:19,155 They are empowered, self-organizing, 545 00:21:19,155 --> 00:21:21,524 self-managing, and cross-functional, 546 00:21:21,524 --> 00:21:23,381 lots of words, but I think you understand what that means. 547 00:21:23,381 --> 00:21:26,192 Most importantly, they deliver tested, working 548 00:21:26,192 --> 00:21:28,198 system software every two weeks. 549 00:21:28,198 --> 00:21:30,748 Not just a working story, or code chucked 550 00:21:30,748 --> 00:21:34,156 into a baseline, a system every two weeks 551 00:21:34,156 --> 00:21:36,298 like a metronome, here's our new system. 552 00:21:36,298 --> 00:21:39,180 What do you think of it, Mr. Customer? 553 00:21:39,180 --> 00:21:40,724 What do you think of it, management team? 554 00:21:40,724 --> 00:21:42,212 Is this, are we building the right system, 555 00:21:42,212 --> 00:21:44,024 is this the thing we want to build. 556 00:21:44,024 --> 00:21:45,496 As you probably are well aware, 557 00:21:45,496 --> 00:21:47,580 there's been quite a bit of debate in the industry 558 00:21:47,580 --> 00:21:49,364 over the last decade, it's like don't we like Scrum. 559 00:21:49,364 --> 00:21:51,374 I like Scrum too, we think Scrum is great, 560 00:21:51,374 --> 00:21:54,780 we love the time boxes, we think more in continuous 561 00:21:54,780 --> 00:21:58,140 flow here, we think Scrum has too much structure 562 00:21:58,140 --> 00:21:59,698 or too much rigor around it. 563 00:21:59,698 --> 00:22:01,652 We'd like to have a continuous flow of value, 564 00:22:01,652 --> 00:22:03,329 we like to use Kanban. 565 00:22:03,329 --> 00:22:06,152 Well I attended a Scrum class, and I attended 566 00:22:06,152 --> 00:22:08,804 a Kanban class, and nobody ever talked about 567 00:22:08,804 --> 00:22:10,724 the actual process of creating code, 568 00:22:10,724 --> 00:22:13,124 for that we need extreme programming. 569 00:22:13,124 --> 00:22:15,944 So this is not a case where we're gonna pick 570 00:22:15,944 --> 00:22:17,836 are we going to use Scrum, are we gonna use Kanban, 571 00:22:17,836 --> 00:22:21,420 are we gonna us XP, we're gonna use them all 572 00:22:21,420 --> 00:22:23,744 in the context that suits us best. 573 00:22:23,744 --> 00:22:25,949 So this is the year, 2017 now folks, 574 00:22:25,949 --> 00:22:27,853 and it's time to move past the method wars 575 00:22:27,853 --> 00:22:30,992 about which team level model works best 576 00:22:30,992 --> 00:22:34,064 and employ the best aspects of all of those 577 00:22:34,064 --> 00:22:35,864 to deliver value more frequently. 578 00:22:35,864 --> 00:22:37,380 Okay, maybe I fibbed a bit. 579 00:22:37,380 --> 00:22:39,824 Something does beat an Agile team, 580 00:22:39,824 --> 00:22:41,880 and that's a team of Agile teams. 581 00:22:41,880 --> 00:22:44,760 There's nothing like the cooperative and collaborative 582 00:22:44,760 --> 00:22:47,116 nature of a group of teams that are working 583 00:22:47,116 --> 00:22:49,449 together as a team of teams, 584 00:22:50,489 --> 00:22:54,632 to deliver value, and now the stack gets bigger, 585 00:22:54,632 --> 00:22:57,120 the system gets bigger, the excitement goes up. 586 00:22:57,120 --> 00:22:59,296 So you might think, well I really liked being 587 00:22:59,296 --> 00:23:01,320 a stand alone Agile team and I had this great 588 00:23:01,320 --> 00:23:03,060 little local environment, but I can only create 589 00:23:03,060 --> 00:23:05,956 this much of a system, could only create a few features. 590 00:23:05,956 --> 00:23:08,324 What if we worked together and combine 591 00:23:08,324 --> 00:23:10,244 your system with my system, and we build 592 00:23:10,244 --> 00:23:12,856 a great great big system, that we spend much 593 00:23:12,856 --> 00:23:16,216 of our time building my piece, and the rest 594 00:23:16,216 --> 00:23:18,376 of my time making sure that the pieces work together, 595 00:23:18,376 --> 00:23:22,499 build a much larger system, that's more fun too, frankly. 596 00:23:22,499 --> 00:23:23,880 So being part of an Agile team, 597 00:23:23,880 --> 00:23:26,296 being part of a team of Agile teams, is a kick. 598 00:23:26,296 --> 00:23:29,520 Also self-managing and self-organizing. 599 00:23:29,520 --> 00:23:31,364 Also delivering fully tested system 600 00:23:31,364 --> 00:23:33,132 increments every two weeks. 601 00:23:33,132 --> 00:23:35,264 Need some things to help with that, 602 00:23:35,264 --> 00:23:38,324 some vision, architecture, UX guidance, you saw 603 00:23:38,324 --> 00:23:40,440 Lean UX on the picture there. 604 00:23:40,440 --> 00:23:42,272 We need a couple other things as well. 605 00:23:42,272 --> 00:23:44,037 We're gonna need to operate on a common cadence, 606 00:23:44,037 --> 00:23:46,528 cuz this is gonna be pretty awkward if our cadences 607 00:23:46,528 --> 00:23:48,572 are different, if this team is operating 608 00:23:48,572 --> 00:23:51,196 on this cadence, let's say they're going really fast, 609 00:23:51,196 --> 00:23:53,337 these guys are a little bit slower, 610 00:23:53,337 --> 00:23:55,036 they don't line up, but when can I integrate my stuff? 611 00:23:55,036 --> 00:23:57,600 I'm in the middle of an iteration, 612 00:23:57,600 --> 00:24:00,932 or sprint here, they are too, they're towards the end, 613 00:24:00,932 --> 00:24:04,169 it's hard to integrate, and until you get you're 614 00:24:04,169 --> 00:24:06,436 complete continuous integration act together, you're 615 00:24:06,436 --> 00:24:08,340 gonna wanna create the points at which you do demonstrate 616 00:24:08,340 --> 00:24:12,402 that full system, so we'll align those teams 617 00:24:12,402 --> 00:24:14,792 to a common set of system increments. 618 00:24:14,792 --> 00:24:17,397 On the ways of estimating, does estimating create value? 619 00:24:17,397 --> 00:24:20,038 Well that's a fun subject, that'll be a discussion 620 00:24:20,038 --> 00:24:21,480 we'll have a little bit later. 621 00:24:21,480 --> 00:24:23,296 But face to face planning for collaboration 622 00:24:23,296 --> 00:24:25,036 and alignment; we're gonna hafta figure out 623 00:24:25,036 --> 00:24:26,792 how to get these people to use that same 624 00:24:26,792 --> 00:24:29,380 basic practice as we meet face to face to do our planning, 625 00:24:29,380 --> 00:24:31,560 we wanna meet face to face to face to face 626 00:24:31,560 --> 00:24:34,516 to make that team, to help that team of teams 627 00:24:34,516 --> 00:24:37,440 to align and work towards a common vision. 628 00:24:37,440 --> 00:24:40,379 Portfolio SAFe, so we take essential SAFe, 629 00:24:40,379 --> 00:24:42,900 which is this lower level here which I described 630 00:24:42,900 --> 00:24:47,372 earlier, and we add to it portfolio constructs. 631 00:24:47,372 --> 00:24:49,754 Not everybody has to concern themselves with that, 632 00:24:49,754 --> 00:24:51,521 we operate in a lot of environments where 633 00:24:51,521 --> 00:24:53,836 they're building, you know, mission critical 634 00:24:53,836 --> 00:24:55,482 systems that's part of a portfolio, 635 00:24:55,482 --> 00:24:58,112 but the portfolio flow of work is not their concern. 636 00:24:58,112 --> 00:25:00,300 However for many of the rest of us it is a concern, 637 00:25:00,300 --> 00:25:02,220 and we need to think about how we'll align 638 00:25:02,220 --> 00:25:05,130 our vision with the enterprise vision, 639 00:25:05,130 --> 00:25:07,483 when we have artifacts to help us do that, 640 00:25:07,483 --> 00:25:10,348 how we apply a much leaner budgeting construct, 641 00:25:10,348 --> 00:25:13,740 and how we influence these various value streams. 642 00:25:13,740 --> 00:25:16,411 Think of value streams as simply teams of teams 643 00:25:16,411 --> 00:25:18,223 working together to deliver value of a type. 644 00:25:18,223 --> 00:25:20,832 How we align that with various types of other artifacts. 645 00:25:20,832 --> 00:25:22,816 So we'll spend some time talking 646 00:25:22,816 --> 00:25:24,359 about portfolio SAFe for sure. 647 00:25:24,359 --> 00:25:27,076 That helps us align strategy and execution. 648 00:25:27,076 --> 00:25:30,716 Large solution SAFe is a new configuration. 649 00:25:30,716 --> 00:25:32,612 Now what I've described here are the out of box 650 00:25:32,612 --> 00:25:34,420 configurations, you saw in the demo there 651 00:25:34,420 --> 00:25:36,764 that I would click a configuration 652 00:25:36,764 --> 00:25:38,560 and show one configuration or another. 653 00:25:38,560 --> 00:25:40,364 These are those configurations. 654 00:25:40,364 --> 00:25:42,900 Large solution SAFe is kind of what grew out 655 00:25:42,900 --> 00:25:44,836 of SAFe for Lean Systems Engineering. 656 00:25:44,836 --> 00:25:46,936 When people that were literally building 657 00:25:46,936 --> 00:25:48,944 satellites and defense systems 658 00:25:48,944 --> 00:25:50,760 and large medical systems, and MRI systems, etc., 659 00:25:50,760 --> 00:25:54,480 said we like what you're doing in software. 660 00:25:54,480 --> 00:25:55,892 You're providing a lot of helpful guidance, 661 00:25:55,892 --> 00:25:58,840 but guess what, that's not exactly our problem. 662 00:25:58,840 --> 00:26:00,580 We're building an MRI system, and yes we have 663 00:26:00,580 --> 00:26:02,680 millions of lines of code, but we also have 664 00:26:02,680 --> 00:26:06,272 thermal considerations, and we have electrical 665 00:26:06,272 --> 00:26:07,105 properties, and optical properties, 666 00:26:07,105 --> 00:26:08,596 and all kinds of things we have to worry about. 667 00:26:08,596 --> 00:26:10,232 So we need some more help with that. 668 00:26:10,232 --> 00:26:12,404 So we worked with those people for, gosh, I think 669 00:26:12,404 --> 00:26:14,804 about a full year, and the sandbox called 670 00:26:14,804 --> 00:26:16,333 SAFe for Lean Systems Engineer, 671 00:26:16,333 --> 00:26:18,736 and we started talking about things like 672 00:26:18,736 --> 00:26:21,240 how do you know what the solution's supposed to do? 673 00:26:21,240 --> 00:26:22,844 Do we just code it and hope it works great 674 00:26:22,844 --> 00:26:24,883 and record everything in a test case? 675 00:26:24,883 --> 00:26:26,998 Or is there some amount of intent for the solution? 676 00:26:26,998 --> 00:26:29,324 Is everything known, or are some things for sure known? 677 00:26:29,324 --> 00:26:32,864 There's a fixed requirement to do this, 678 00:26:32,864 --> 00:26:35,340 have to be able to support for people on that ride, 679 00:26:35,340 --> 00:26:37,857 or have to be able to have to be able to have 680 00:26:37,857 --> 00:26:39,555 a satellite resolution, a satellite camera 681 00:26:39,555 --> 00:26:41,340 resolution of X, but some of which is variable. 682 00:26:41,340 --> 00:26:44,053 Goodness, maybe I can do interpolation 683 00:26:44,053 --> 00:26:47,912 of that data to achieve an apparent higher resolution. 684 00:26:47,912 --> 00:26:50,312 Other things, what happens when we have 685 00:26:50,312 --> 00:26:53,775 many ARTs that are necessary to build 686 00:26:53,775 --> 00:26:55,720 that satellite system? 687 00:26:55,720 --> 00:26:57,569 Well we're going to build a solution train, 688 00:26:57,569 --> 00:26:59,880 a virtual organizational construct, 689 00:26:59,880 --> 00:27:02,820 that brings the ARTs and suppliers together, 690 00:27:02,820 --> 00:27:05,189 and uses typically different language 691 00:27:05,189 --> 00:27:08,037 to talk about the things we need to do 692 00:27:08,037 --> 00:27:10,335 to evolve that system. 693 00:27:10,335 --> 00:27:12,961 We're going to plan before the ARTs, 694 00:27:12,961 --> 00:27:15,661 and probably a little bit post planning, 695 00:27:15,661 --> 00:27:18,285 to make sure that what we planned here makes sense 696 00:27:18,285 --> 00:27:21,733 across all the ARTs, and vision, imagine that this 697 00:27:21,733 --> 00:27:23,745 is a 3-D plane, with another ART behind that. 698 00:27:23,745 --> 00:27:25,981 That's the large solution level. 699 00:27:25,981 --> 00:27:27,989 And that allows us to coordinate our ARTs 700 00:27:27,989 --> 00:27:30,241 and suppliers again, with this 701 00:27:30,241 --> 00:27:32,189 virtual organizational construct. 702 00:27:32,189 --> 00:27:34,333 We'll talk about virtual versus line organizations 703 00:27:34,333 --> 00:27:36,569 a little later on in the course. 704 00:27:36,569 --> 00:27:38,461 Full SAFe, okay well what if I'm building 705 00:27:38,461 --> 00:27:41,221 a satellite and a big software system, 706 00:27:41,221 --> 00:27:43,018 and I want all of the above, so maybe an example 707 00:27:43,018 --> 00:27:46,605 would be, I'm building an automotive entertainment 708 00:27:46,605 --> 00:27:49,665 system for one of the big automotive suppliers, 709 00:27:49,665 --> 00:27:53,832 and my context is I'm building this infotainment system. 710 00:27:59,238 --> 00:28:03,449 Okay, that's great, so I have for my customer 711 00:28:03,449 --> 00:28:06,733 who's out here, this guy here, I have a specific 712 00:28:06,733 --> 00:28:08,941 set of requirements to build that system 713 00:28:08,941 --> 00:28:11,521 in a way that meets their needs. 714 00:28:11,521 --> 00:28:12,961 That's fine. 715 00:28:12,961 --> 00:28:13,921 Is that my only concern? 716 00:28:13,921 --> 00:28:15,913 No, it turns out that this system, 717 00:28:15,913 --> 00:28:18,705 the solution, is also part of my portfolio, 718 00:28:18,705 --> 00:28:20,969 so I don't just ship it to that customer, 719 00:28:20,969 --> 00:28:23,429 so I have to have more than the large solution context, 720 00:28:23,429 --> 00:28:25,785 I need to be able to understand how that plays 721 00:28:25,785 --> 00:28:27,013 in the portfolio. 722 00:28:27,013 --> 00:28:29,369 So if you're in a circumstance where you're 723 00:28:29,369 --> 00:28:31,843 building large solutions, that are sold 724 00:28:31,843 --> 00:28:33,973 not just to a single entity, 725 00:28:33,973 --> 00:28:36,190 a single user, but to multiple customers, 726 00:28:36,190 --> 00:28:38,761 then you're going to have both the large solution 727 00:28:38,761 --> 00:28:40,753 and the portfolio contexts. 728 00:28:40,753 --> 00:28:42,958 So like I said, full SAFe has it all. 729 00:28:42,958 --> 00:28:44,878 So navigable, everything's the same, 730 00:28:44,878 --> 00:28:47,145 you can operate with any of these configurations 731 00:28:47,145 --> 00:28:50,478 that we described with no fear of losing 732 00:28:51,313 --> 00:28:52,741 any of the value. 733 00:28:52,741 --> 00:28:54,241 You've seen a few other things over here. 734 00:28:54,241 --> 00:28:56,161 You've seen this tool palette move around a little bit 735 00:28:56,161 --> 00:28:58,921 or actually expand and collapse based 736 00:28:58,921 --> 00:29:00,841 on the things you might need in that case. 737 00:29:00,841 --> 00:29:03,165 You've seen the foundation not changed, 738 00:29:03,165 --> 00:29:04,740 because the foundation is the same 739 00:29:04,740 --> 00:29:07,076 in all the configurations of SAFe.