1 00:00:04,281 --> 00:00:06,541 G'day and welcome to Amazing Apps. 2 00:00:09,107 --> 00:00:12,357 I'm your host, Microsoft MVP, Neil Benson. 3 00:00:14,795 --> 00:00:16,935 I'm on a mission to help you master Agile 4 00:00:16,935 --> 00:00:19,705 practices and build amazing apps on the 5 00:00:19,975 --> 00:00:22,755 Microsoft Power Platform and Dynamics 365. 6 00:00:25,393 --> 00:00:27,033 Amazing Apps is the result of my 7 00:00:27,043 --> 00:00:29,253 curiosity and experiments with new 8 00:00:29,253 --> 00:00:31,463 ways of building amazing business 9 00:00:31,523 --> 00:00:33,263 apps and high performing teams. 10 00:00:33,673 --> 00:00:35,283 It's full of advice from my guests 11 00:00:35,643 --> 00:00:37,893 and examples from some of my work over 12 00:00:37,893 --> 00:00:39,733 the last few years leading business 13 00:00:39,733 --> 00:00:41,703 applications, teams, and practices. 14 00:00:42,423 --> 00:00:43,993 If you enjoy this episode, head 15 00:00:43,993 --> 00:00:45,813 over to https://amazingapps.Show 16 00:00:45,993 --> 00:00:47,093 for additional resources. 17 00:00:47,513 --> 00:00:49,293 You'll find more episodes of Amazing Apps 18 00:00:49,493 --> 00:00:51,413 as well as my videos, free workshops, 19 00:00:51,463 --> 00:00:53,543 ebooks, and my online training courses. 20 00:00:54,383 --> 00:00:56,023 In this episode, I'm going to try 21 00:00:56,023 --> 00:00:58,053 and persuade you to continue learning 22 00:00:58,233 --> 00:01:00,123 through experimentation as we 23 00:01:00,323 --> 00:01:03,023 embark on our AI adoption journey. 24 00:01:03,433 --> 00:01:04,013 We're going to be talking 25 00:01:04,013 --> 00:01:06,043 a lot about experiments. 26 00:01:07,043 --> 00:01:08,873 But let's start with smallpox. 27 00:01:09,483 --> 00:01:11,593 When's the last time you or 28 00:01:11,593 --> 00:01:13,663 someone you know well had smallpox? 29 00:01:14,463 --> 00:01:15,823 I bet it's never, at 30 00:01:15,823 --> 00:01:16,913 least I hope it's never. 31 00:01:17,433 --> 00:01:18,573 According to the World Health 32 00:01:18,573 --> 00:01:20,483 Organization, people have been trying to 33 00:01:20,483 --> 00:01:23,143 inoculate themselves against smallpox by 34 00:01:23,143 --> 00:01:26,083 exposing themselves to the virus since the 35 00:01:26,083 --> 00:01:29,053 15th century, maybe as early as 200 BC. 36 00:01:30,772 --> 00:01:33,402 In 1721, Lady Mary Wortley Montagu 37 00:01:33,712 --> 00:01:36,072 brought smallpox inoculation to Europe 38 00:01:36,402 --> 00:01:37,922 by asking that her two daughters 39 00:01:38,172 --> 00:01:40,462 be inoculated against smallpox. 40 00:01:40,982 --> 00:01:42,132 That was a practice she 41 00:01:42,132 --> 00:01:43,282 had observed in Turkey. 42 00:01:43,792 --> 00:01:45,382 By all accounts, she was quite 43 00:01:45,382 --> 00:01:47,012 the adventuress of her day. 44 00:01:48,072 --> 00:01:51,612 Fifty years later, in 1774, Benjamin 45 00:01:51,612 --> 00:01:53,492 Jesty makes another breakthrough. 46 00:01:54,052 --> 00:01:55,882 Testing his hypothesis, that 47 00:01:55,882 --> 00:01:58,522 infection with cowpox, a bovine 48 00:01:58,522 --> 00:02:00,472 virus which can spread to humans, 49 00:02:00,682 --> 00:02:02,872 could protect a person from smallpox. 50 00:02:03,730 --> 00:02:05,790 He and his family were spared from the 51 00:02:05,790 --> 00:02:08,250 smallpox infection that swept through 52 00:02:08,430 --> 00:02:10,710 the southwest of England in 1774. 53 00:02:11,340 --> 00:02:13,270 Jesty was one of several people 54 00:02:13,410 --> 00:02:15,320 thought to have practiced inoculation 55 00:02:15,330 --> 00:02:17,530 around this time, but the credit for 56 00:02:17,530 --> 00:02:19,810 inventing vaccination is generally 57 00:02:19,820 --> 00:02:21,130 given to our next character. 58 00:02:21,850 --> 00:02:24,740 Twenty years later, in 1796, a 59 00:02:24,750 --> 00:02:26,480 British doctor, Edward Jenner, 60 00:02:26,650 --> 00:02:28,150 conducted one of the bravest 61 00:02:28,150 --> 00:02:29,840 experiments I've ever heard of. 62 00:02:29,840 --> 00:02:32,970 He swabbed the ugly cowpox lesion 63 00:02:32,990 --> 00:02:35,500 of a milkmaid and used it to infect 64 00:02:35,670 --> 00:02:37,860 an 8 year old boy, James Phipps. 65 00:02:38,785 --> 00:02:41,045 If any of you know any 8 year old boys, 66 00:02:41,295 --> 00:02:43,005 this isn't a practice I would recommend. 67 00:02:43,705 --> 00:02:45,505 Phipps was unwell and suffered a local 68 00:02:45,505 --> 00:02:47,815 reaction, but he made a full recovery. 69 00:02:48,285 --> 00:02:49,315 So what did Jenner do? 70 00:02:49,905 --> 00:02:53,535 Two months later, in July 1776, he tested 71 00:02:53,535 --> 00:02:55,895 Phipps resistance by infecting him with 72 00:02:55,895 --> 00:02:57,845 matter from a human smallpox lesion. 73 00:02:58,565 --> 00:03:01,395 Cowpox in humans results in ugly 74 00:03:01,395 --> 00:03:04,195 lesions, often on the hands and arms and 75 00:03:04,195 --> 00:03:06,985 face, but it's mild and rarely deadly. 76 00:03:07,615 --> 00:03:09,915 Smallpox, however, is far more 77 00:03:09,945 --> 00:03:13,245 infectious and in 1776 it often 78 00:03:13,245 --> 00:03:15,835 resulted in a slow, painful death. 79 00:03:16,465 --> 00:03:20,175 It's reported to have been responsible 80 00:03:20,255 --> 00:03:22,465 for between 10 percent and 20 percent 81 00:03:22,525 --> 00:03:24,845 of all deaths in the 18th century. 82 00:03:25,835 --> 00:03:27,555 Whatever happened to 8 year old Phipps? 83 00:03:27,925 --> 00:03:29,505 Well, he remained in good health 84 00:03:29,745 --> 00:03:31,735 despite the smallpox exposure. 85 00:03:32,095 --> 00:03:33,685 He's considered to be the first 86 00:03:33,685 --> 00:03:36,385 person vaccinated against smallpox. 87 00:03:37,870 --> 00:03:39,640 And did you know, the word vaccination 88 00:03:39,640 --> 00:03:42,210 is derived from vacca, Latin for cow. 89 00:03:42,680 --> 00:03:43,530 This is a painting of 90 00:03:43,570 --> 00:03:45,170 Benjamin Jesty's cow, Blossom. 91 00:03:45,570 --> 00:03:46,730 The most famous cow in the 92 00:03:46,730 --> 00:03:49,050 world, at least in 1774. 93 00:03:50,020 --> 00:03:52,120 Other experiments since then by 94 00:03:52,130 --> 00:03:54,600 scientists have led to vaccinations 95 00:03:54,600 --> 00:03:56,800 against over 20 human diseases. 96 00:03:57,540 --> 00:03:59,600 Receiving vaccines has become routine 97 00:03:59,830 --> 00:04:02,500 for many of us, especially since 2020. 98 00:04:02,950 --> 00:04:04,680 Many of us wouldn't be here if our 99 00:04:04,710 --> 00:04:06,770 antecedents hadn't been vaccinated 100 00:04:07,000 --> 00:04:10,020 against smallpox and other deadly viruses. 101 00:04:11,250 --> 00:04:14,020 In 1996, I was studying biochemistry 102 00:04:14,230 --> 00:04:15,320 at the University of Edinburgh 103 00:04:15,720 --> 00:04:17,840 where I spliced the gene from green 104 00:04:17,840 --> 00:04:19,650 fluorescent protein, which is found 105 00:04:19,650 --> 00:04:21,700 in the jellyfish, Aquorea victoria, 106 00:04:22,030 --> 00:04:23,840 through a bacterial vector into 107 00:04:23,850 --> 00:04:26,430 yeast, saccharomyces cerevisiae. 108 00:04:26,870 --> 00:04:28,500 According to my professor, our 109 00:04:28,500 --> 00:04:30,400 experiments were related to gene 110 00:04:30,400 --> 00:04:32,030 targeting and cancer research. 111 00:04:32,748 --> 00:04:34,518 Through ultraviolet microscopy, we 112 00:04:34,518 --> 00:04:36,561 could see exactly where inside the 113 00:04:36,561 --> 00:04:39,381 yeast cell DNA was being expressed and 114 00:04:39,381 --> 00:04:41,181 proteins were subsequently located. 115 00:04:41,741 --> 00:04:43,271 My goal was just to make 116 00:04:43,561 --> 00:04:44,421 glow in the dark beer. 117 00:04:45,041 --> 00:04:46,321 Can you imagine traffic 118 00:04:46,321 --> 00:04:47,431 cop with a UV torch? 119 00:04:47,921 --> 00:04:49,211 Honestly, officer, I 120 00:04:49,211 --> 00:04:50,091 haven't been drinking. 121 00:04:51,561 --> 00:04:52,801 But I found the conversational 122 00:04:52,801 --> 00:04:55,461 skills of baker's yeast to be pretty 123 00:04:55,461 --> 00:04:57,691 poor compared to C# developers. 124 00:04:58,011 --> 00:05:00,011 So I ended up pursuing a career 125 00:05:00,831 --> 00:05:02,481 with the IT crowd instead. 126 00:05:03,311 --> 00:05:04,731 But my passion for running 127 00:05:04,741 --> 00:05:06,591 experiments hasn't abated. 128 00:05:07,141 --> 00:05:09,281 Today, I'm the co founder of SuperWire. 129 00:05:09,341 --> 00:05:12,081 ai, a Microsoft partner and independent 130 00:05:12,081 --> 00:05:14,121 software vendor building engagement 131 00:05:14,121 --> 00:05:16,481 applications for superannuation funds on 132 00:05:16,521 --> 00:05:19,141 Power Platform, Dynamics 365, and Azure. 133 00:05:19,681 --> 00:05:22,121 I'm also the founder of Customery, an 134 00:05:22,131 --> 00:05:24,191 online training provider helping Microsoft 135 00:05:24,191 --> 00:05:26,551 teams adopt and master Agile practices. 136 00:05:27,151 --> 00:05:29,051 In both businesses, we love 137 00:05:29,241 --> 00:05:31,211 learning through experimentation. 138 00:05:32,231 --> 00:05:34,451 We start with a hypothesis, run a short 139 00:05:34,451 --> 00:05:36,361 experiment to test the hypothesis, 140 00:05:36,661 --> 00:05:39,011 review the results, and reassess our 141 00:05:40,331 --> 00:05:42,721 hypothesis to improve our knowledge. 142 00:05:43,461 --> 00:05:45,081 Instead of learning through experiments, 143 00:05:45,531 --> 00:05:47,731 lots of development teams attempt to 144 00:05:47,901 --> 00:05:49,901 design everything up front, in the 145 00:05:49,901 --> 00:05:52,211 belief that if we could just understand 146 00:05:52,211 --> 00:05:53,981 enough at the analysis and design 147 00:05:53,981 --> 00:05:56,061 phase, that everything will be alright. 148 00:05:57,321 --> 00:05:58,811 If you are analysing your users 149 00:05:58,811 --> 00:06:00,801 requirements up front, and designing 150 00:06:00,801 --> 00:06:02,611 your solution in advance, you're 151 00:06:02,611 --> 00:06:04,671 doing it at the point of peak 152 00:06:04,811 --> 00:06:07,501 ignorance, also known as Mount Stupid. 153 00:06:08,391 --> 00:06:09,591 At the start of your project, 154 00:06:09,731 --> 00:06:11,041 your team knows least about 155 00:06:11,041 --> 00:06:12,081 the users and their needs. 156 00:06:12,566 --> 00:06:14,076 And your users know least about 157 00:06:14,086 --> 00:06:15,136 the application you're building. 158 00:06:15,716 --> 00:06:17,836 Instead, if you can defer the requirements 159 00:06:17,836 --> 00:06:20,216 analysis until the last possible moment 160 00:06:20,476 --> 00:06:21,746 before you need to start developing 161 00:06:21,746 --> 00:06:23,486 the feature, you'll have learned a lot 162 00:06:23,486 --> 00:06:24,926 more about the requirements by then. 163 00:06:25,516 --> 00:06:27,206 Don't spend months analyzing 164 00:06:27,216 --> 00:06:28,846 requirements before development starts. 165 00:06:29,376 --> 00:06:31,386 Instead, work in short bursts. 166 00:06:31,387 --> 00:06:33,596 Keep the users involved in planning your 167 00:06:33,596 --> 00:06:35,666 experiments and reviewing the results. 168 00:06:36,866 --> 00:06:38,596 Learning through experimentation, 169 00:06:39,066 --> 00:06:40,316 working in short increments. 170 00:06:40,831 --> 00:06:42,521 Emergent analysis and design. 171 00:06:42,831 --> 00:06:44,111 Collaborating with users 172 00:06:44,111 --> 00:06:44,911 while building the app. 173 00:06:45,551 --> 00:06:47,621 We've got a label for working like this. 174 00:06:48,041 --> 00:06:50,401 It's called Agile Software Development. 175 00:06:51,241 --> 00:06:53,041 Especially the Scrum framework, which 176 00:06:53,041 --> 00:06:55,371 is founded on empiricism, which is 177 00:06:55,381 --> 00:06:57,111 the theory that we learn from the 178 00:06:57,111 --> 00:06:59,051 experience derived from our senses. 179 00:06:59,841 --> 00:07:01,991 That is, complex solutions 180 00:07:02,161 --> 00:07:03,541 can't be designed up front. 181 00:07:03,951 --> 00:07:06,251 We need to learn through experimentation. 182 00:07:07,346 --> 00:07:08,716 Let me give you an example 183 00:07:08,726 --> 00:07:10,366 of how we experiment while 184 00:07:10,366 --> 00:07:12,086 building Microsoft business apps. 185 00:07:13,016 --> 00:07:14,636 One of my teams is currently working 186 00:07:14,636 --> 00:07:17,286 for a Queensland government department. 187 00:07:17,426 --> 00:07:18,896 They register and monitor the 188 00:07:18,896 --> 00:07:20,686 training contracts for Queensland's 189 00:07:20,866 --> 00:07:22,276 trainees and apprentices. 190 00:07:23,486 --> 00:07:25,436 Every year, they process 90,000 191 00:07:25,457 --> 00:07:27,556 expense claims submitted by trainees 192 00:07:27,776 --> 00:07:28,966 who have attended an approved 193 00:07:29,036 --> 00:07:30,566 training class away from home. 194 00:07:31,456 --> 00:07:34,256 63,000 of these claims are PDF forms 195 00:07:34,496 --> 00:07:36,106 that are emailed to the department, 196 00:07:36,396 --> 00:07:39,516 and 17, 000 are submitted online via 197 00:07:39,516 --> 00:07:41,756 a webpage developed 12 years ago. 198 00:07:42,576 --> 00:07:44,656 A 12-year-old .NET web app is 199 00:07:44,656 --> 00:07:46,126 considered pretty modern by 200 00:07:46,126 --> 00:07:47,276 this department's standards. 201 00:07:47,916 --> 00:07:49,716 How could we improve the trainees 202 00:07:49,746 --> 00:07:52,016 expense claim experience and the 203 00:07:52,016 --> 00:07:53,666 department's processing efficiency? 204 00:07:54,886 --> 00:07:56,976 The first idea we had was a new 205 00:07:57,196 --> 00:08:00,096 mobile-optimized Power Pages site that 206 00:08:00,096 --> 00:08:02,626 would connect directly to Dataverse 207 00:08:02,866 --> 00:08:04,596 where the trainee data is already stored. 208 00:08:05,206 --> 00:08:06,536 We would automatically calculate 209 00:08:06,536 --> 00:08:07,576 the distance from the trainee's 210 00:08:07,596 --> 00:08:09,186 home to the training location. 211 00:08:09,506 --> 00:08:11,036 And we already provide a portal for 212 00:08:11,036 --> 00:08:12,626 the training provider to confirm 213 00:08:12,626 --> 00:08:13,846 the trainee attended the training. 214 00:08:14,196 --> 00:08:16,306 And then we would send the 215 00:08:16,526 --> 00:08:18,236 payment to SAP for processing. 216 00:08:19,081 --> 00:08:21,431 But the department can't force trainees to 217 00:08:21,431 --> 00:08:23,711 use a webpage, and many of them are handed 218 00:08:24,341 --> 00:08:26,741 PDF forms by the tutor at the end of the 219 00:08:26,741 --> 00:08:28,591 training course, and it's easy for them 220 00:08:28,801 --> 00:08:31,001 to get the form approved there and then. 221 00:08:31,971 --> 00:08:33,721 Instead, we're going to experiment 222 00:08:33,731 --> 00:08:35,591 with the Power Platform's AI builder 223 00:08:35,891 --> 00:08:38,211 by training a form processing model to 224 00:08:38,211 --> 00:08:40,711 read the PDF expense claim documents, 225 00:08:40,951 --> 00:08:43,251 turn them into a digital expense claim 226 00:08:43,251 --> 00:08:45,281 record in Dataverse so that we can 227 00:08:45,301 --> 00:08:47,281 process most of them automatically. 228 00:08:47,961 --> 00:08:49,221 We call this type of work a 229 00:08:49,251 --> 00:08:51,251 spike in our product backlog. 230 00:08:51,926 --> 00:08:53,546 Like a rock clamors spike. 231 00:08:53,696 --> 00:08:56,066 Our spikes allow us to safely explore 232 00:08:56,066 --> 00:08:58,076 a new rock face and discover if 233 00:08:58,076 --> 00:09:00,056 there is a path towards progress. 234 00:09:00,576 --> 00:09:02,286 At the same time, our risk of falling and 235 00:09:02,286 --> 00:09:04,626 dying is reduced because we time box the 236 00:09:04,626 --> 00:09:07,146 spike and contain it into a fixed amount 237 00:09:07,146 --> 00:09:09,206 of effort within our two-week sprint. 238 00:09:10,256 --> 00:09:11,636 During the sprint review, we'll report 239 00:09:11,636 --> 00:09:13,706 the results of our spike back to our 240 00:09:13,706 --> 00:09:16,096 stakeholders and invite their feedback 241 00:09:16,266 --> 00:09:18,586 about whether or not to pursue that 242 00:09:18,586 --> 00:09:20,816 solution or try another experiment. 243 00:09:21,876 --> 00:09:23,566 I remember Frieda, our CRM 244 00:09:23,586 --> 00:09:24,766 product owner at the University 245 00:09:24,766 --> 00:09:26,606 of New South Wales, wasn't happy 246 00:09:26,896 --> 00:09:28,996 that all our spikes went well. 247 00:09:30,096 --> 00:09:32,536 If every experiment succeeds and proves 248 00:09:32,536 --> 00:09:34,496 your hypothesis, said Frieda, then it's 249 00:09:34,496 --> 00:09:36,981 because your experiments were too safe. 250 00:09:37,521 --> 00:09:39,031 It's only when half of your spikes 251 00:09:39,041 --> 00:09:41,101 fail do you know that you're 252 00:09:41,111 --> 00:09:43,151 being bold enough and building an 253 00:09:43,151 --> 00:09:44,881 amazing new business application. 254 00:09:46,451 --> 00:09:47,731 Our government department is also 255 00:09:47,731 --> 00:09:49,661 considering implementing a new business 256 00:09:49,661 --> 00:09:51,671 rules engine to replace the 20 year 257 00:09:51,671 --> 00:09:53,411 old rules engine that supports the 258 00:09:53,411 --> 00:09:55,001 legacy PowerBuilder application 259 00:09:55,231 --> 00:09:56,701 we're replacing with Power Apps. 260 00:09:57,191 --> 00:09:58,421 When a new training contract is 261 00:09:58,431 --> 00:10:00,181 submitted to the department, they need 262 00:10:00,181 --> 00:10:01,721 to validate the trainee's details, 263 00:10:02,061 --> 00:10:03,761 the employer's details, the workplace 264 00:10:03,761 --> 00:10:05,981 location, the contract dates, the training 265 00:10:05,981 --> 00:10:07,461 organization, the training course. 266 00:10:07,951 --> 00:10:09,421 There are hundreds of validations 267 00:10:09,441 --> 00:10:11,171 to perform on each contract, and 268 00:10:11,171 --> 00:10:13,161 thousands of rules in the rules engine. 269 00:10:13,778 --> 00:10:15,548 Instead of a business rules engine with 270 00:10:15,548 --> 00:10:18,348 a fixed set of deterministic rules, could 271 00:10:18,348 --> 00:10:21,088 we use AI to validate training contracts? 272 00:10:21,638 --> 00:10:23,708 Could we build a model of valid training 273 00:10:23,708 --> 00:10:26,358 contracts, then train a co pilot to 274 00:10:26,358 --> 00:10:28,828 spot invalid training contracts, and 275 00:10:28,828 --> 00:10:30,948 ask it to validate all the new training 276 00:10:30,948 --> 00:10:32,378 contracts coming into the department? 277 00:10:32,378 --> 00:10:34,817 Arguably, this approach is not actually 278 00:10:34,817 --> 00:10:36,443 artificial intelligence, it's machine 279 00:10:36,443 --> 00:10:38,881 learning, because the system will be 280 00:10:38,881 --> 00:10:40,914 identifying patterns in the contracts 281 00:10:40,914 --> 00:10:43,203 provided to it And improving its 282 00:10:43,203 --> 00:10:45,143 decision making capability based on 283 00:10:45,143 --> 00:10:47,043 our feedback about new contracts. 284 00:10:47,783 --> 00:10:49,163 Whatever we call it, I think it's 285 00:10:49,163 --> 00:10:50,883 an interesting hypothesis to test. 286 00:10:51,568 --> 00:10:53,448 What's the smallest, useful experiment 287 00:10:53,478 --> 00:10:55,288 we could conduct to help us advance our 288 00:10:55,288 --> 00:10:58,378 knowledge about whether AI, really it's 289 00:10:58,378 --> 00:11:00,838 ML, could validate training contracts 290 00:11:01,048 --> 00:11:02,838 without a hard coded rules engine? 291 00:11:03,648 --> 00:11:05,148 Well, we start Sprint 1 on Monday. 292 00:11:05,358 --> 00:11:06,888 If you follow me on LinkedIn or 293 00:11:06,888 --> 00:11:08,678 subscribe to my podcast, Amazing 294 00:11:08,688 --> 00:11:10,238 Apps, I'll let you know the results. 295 00:11:10,388 --> 00:11:11,798 I love building in public. 296 00:11:12,368 --> 00:11:13,878 Until then, experiment. 297 00:11:14,458 --> 00:11:16,568 Find a hypothesis, run a test, 298 00:11:16,898 --> 00:11:18,458 learn from the results, share the 299 00:11:18,458 --> 00:11:20,068 outcomes with your stakeholders, or 300 00:11:20,078 --> 00:11:21,638 better yet, share them in public. 301 00:11:22,708 --> 00:11:24,753 But, please don't experiment on 8 302 00:11:24,753 --> 00:11:27,073 year old boys or infect anyone with 303 00:11:27,073 --> 00:11:28,803 a deadly disease in your attempts 304 00:11:28,803 --> 00:11:30,643 to harness artificial intelligence. 305 00:11:31,253 --> 00:11:31,903 Thanks for listening 306 00:11:32,043 --> 00:11:32,833 or thanks for watching. 307 00:11:32,833 --> 00:11:34,253 I hope you enjoyed this Amazing 308 00:11:34,263 --> 00:11:35,713 Apps episode and found it useful. 309 00:11:36,443 --> 00:11:37,473 If you want to accelerate your 310 00:11:37,473 --> 00:11:38,963 career by building amazing Power 311 00:11:38,963 --> 00:11:41,133 Platform and Dynamics 365 apps your 312 00:11:41,133 --> 00:11:43,235 stakeholders love, then join me 313 00:11:43,235 --> 00:11:44,886 in my free interactive workshop. 314 00:11:45,048 --> 00:11:46,978 Inside, I share the three secrets 315 00:11:47,158 --> 00:11:49,498 to successfully using Scrum to build 316 00:11:49,528 --> 00:11:51,268 agile apps so that you can deliver 317 00:11:51,268 --> 00:11:53,008 projects faster, under budget, 318 00:11:53,108 --> 00:11:55,518 have more fun, and get promoted. 319 00:11:59,066 --> 00:12:00,316 Register today at 320 00:12:00,316 --> 00:12:03,336 https://customery.com/3secrets. 321 00:12:03,706 --> 00:12:05,616 You'll also find that link in the episode 322 00:12:05,646 --> 00:12:07,736 description, in your podcast player, 323 00:12:07,916 --> 00:12:09,906 or in the YouTube video description. 324 00:12:13,358 --> 00:12:15,408 Until next time, keep experimenting.