Scrum is by far the most used Agile framework. In this video, I'll take you from Waterfall.. to Agile... to the basics of Scrum.
Grab your FREE Scrum Cheat Sheet: https://www.developmentthatpays.com/cheatsheets/scrum
The Scrum Guide: https://www.scrumguides.org/
→ SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe
131. Scrum Overview - [Scrum Basics 2019] + FREE Cheat Sheet
If you've found this video, the chances are you were just searching for Scrum. And if so, I have a fantastic video for you. Sadly, there won't be any of this. But there will be some of this. And just a sprinkling of this. And if you hang around to the end, I'll tell you how to get your hands on this rather lovely cheat sheet. Hi, my name is Gary Strong, welcome to Development That Pays. We do a video like this every Wednesday. Sometimes every other Wednesday. And it would be great to have you along. Click that red button to subscribe and remember to hit the bell so you don't miss a thing. Scrum, as I'm sure you're well aware, is one of a number of Agile methodologies. Hmmm, seems there's a lie detector in operation. It's true though, Scrum is not prescriptive, it doesn't prescribe a specific method, so it's more correctly referred to as a framework. So yes, Scrum is one of a number of Agile frameworks. And like all Agile approaches, it is an incremental process. Is that right, is it incremental Or should that be iterative In fact, it's both: incremental and iterative. As we shall soon see. For now, I'm going to back up just a little bit. For most of us in business our job is to build something, be it a product or service, and deliver it to a customer. But build and deliver what Well, something that the customer wants. Something that the customer values. Trouble is, it's devilishly difficult to work out what a customer wants. Sure we could commission some research, and spend months designing, even more months building, and a few weeks testing, but we're highly likely to find out that we missed the mark, that we spent months, possibly years of our lives, producing something that the customer just doesn't want. Or perhaps something that the customer did want, but doesn't want anymore. All that time, all that money, wasted, down the drain. What you see here is usually described as a Waterfall process. So named because work cascades from one process to the next. It's a death-or-glory, winner-takes-all kind of approach. You get just one shot to get it right. Now me, I'm not much of a gambling man, I'd much prefer to have more than one bite at the cherry, more than one chance to get it right. And that's where Agile comes in. Instead of attempting to deliver the entire thing, we instead deliver in small increments. That's the incremental that I mentioned earlier. Now why would we want to deliver in a piecemeal fashion Well, for one thing, the sooner we deliver something of value to the customer, the sooner we start to get paid, which is always a good thing. But more importantly, every time we deliver something to the customer, we get the opportunity to learn. Did it go down well, or did it go down like a lead balloon Does the customer want more of the same Or do we need to change tack Notice how this gives us the luxury of being wrong. Incremental delivery means we have plenty more chances to get it right. To give you a couple of simple analogies. In Waterfall, the assumption is that we're always on the right track. So a bit like throwing a rock and expecting to always hit the target. In Agile, the assumption is the exact opposite. That we will probably get things wrong. But that we will be able to learn and adjust our course. Much like an airplane in flight. Time to flesh this out a bit. We decide what to build, remember, something small. We build it, deliver it, and learn. Feeding that learning back into the system, before deciding what to build next. Building it, delivering it, and so on. These are the increments, the things that get delivered to the customer. These are the iterations, like I said before, Agile is both an incremental and an iterative process. Okay, we've talked about Waterfall, we've talked about Agile it's now time to get into the detail of Scrum. Ladies and gentlemen, allow me to introduce you to your Scrum team. We have the Development Team, the Product Owner, and the Scrum Master. The Development Team as I'm sure you'd expect is responsible for delivery. The product owner is responsible for the evolution of the product. And then there's the Scrum Master. Now that term, Master, is slightly unfortunate, because there's no command and control here.