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.

= = = = = = = = = = = =

New for 2024: my best-ever training:
"How Your Agile Teams Can Achieve Predictability and Productivity WITHOUT Burnout"
→ https://www.developmentthatpays.com/w...

= = = = = = = = = = = =

Grab your FREE Scrum Cheat Sheet: https://www.developmentthatpays.com/c...


The Scrum Guide: https://www.scrumguides.org/






-------------------
131. Scrum Overview + FREE Cheat Sheet
#AgileScrum #DevelopmentThatPays

Scrum, as I’m sure you’re aware, is one of a number of Agile Methodologies. Oops. One line in and I’m made a mistake: Scrum is not a Methodology. Scrum doesn’t prescribe a specific method: it’s more correctly described as a Framework. So, yes: Scrum is one of a number of Agile Frameworks. And like all Agile approaches, it is an iterative process. Is that right Is it iterative Or is it incremental In fact it’s both iterative AND incremental… as we’ll see in due course. Why Agile --- For now I’m going to back up a little. For most of us in business, our job is to build or develop something - be it a product or service - and deliver it to a customer or customers. But build what Well, something that the customer wants. Something that the customer values Trouble is, it’s devilishly difficult to figure out what a customer wants. Yes we could commission research. And spend months designing, building.. Testing… But we’re likely to find that we’ve missed the mark: We’re created something that the customer doesn't want. Or something that customer did want. You know, in the past. But not now. All that time - MONTHS! - all that money - wasted What you see here is usually described as Waterfall process. So named because work cascades from one process to the next. It’s a death-or-glory, winner-takes-all approach. You got one shot to get it right. Me, I’m not a gambling man. I prefer to have more bites at the cherry. More chances to get things right. And that’s where Agile comes in The Agile Process --- Instead of delivering the entire thing, we break things down and deliver a piece at a time. We deliver in small increments. That’s the “incremental” that I mentioned earlier. Why would we want to deliver in a piecemeal fashion Well, the sooner we get something into the hands of the customer, the sooner we get paid. (And that’s 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 Are we on the right track Does the customer want more of the same, or do we need to change tack Do we need to adjust out course Notice how this gives us the luxury of being wrong! Incremental delivery means that we have plenty more opportunities to get it right. Notice also that we no longer have to rely on what the customer says she wants. If you want a simple analogy: In waterfall, the assumption is that we’re on the right track. Much Like throwing a rock at a target In Agile, the assumption is the exact opposite. that we’ll get it wrong…. But that we’ll also get the opportunity to learn… and to correct our course. Meat on the bones ---- Time to flesh this out a bit: Decide what to build - remember, something small. Build it Deliver it And learn Feed that learning back into the system. Decide what’s the next thing to build Deliver it… And so on These are the increments. And this feedback loop - and the fact that we go round and round - these are the iterations . Scrum ---- We’ve talked about waterfall. We‘ve talked about Agile. I think it’s time we got into the details of Scrum. Allow me to introduce the team: Development Team The Product Owner The Scrum Master The development team is responsible for delivery. The Product Owner is responsible for the “evolution” of the product. And then there’s the Scrum Master. The title is slightly unfortunate: there’s no command and control role here. The role is very much one of servant leader: helping the other to develop and maintain good habits. Let’s give these people some tools to work with. This is the Product Backlog What’s the product Product Backlog I hear you ask Feedback from the customer, together with input from other stakeholders, goes in to the Product Backlog. The Product Backlog is a prioritised list of (mostly) User Stories. It is maintained and managed by the Product Owner. It is a dynamic list. It can - it must - change all the time. The Sprint --- Okay, we have our Product Backlog and we have our Scrum Team.. We’re ready to set to work. The defining property of Scrum is,
   • Scrum Overview + FREE Cheat Sheet