Scrum Basics for Absolute Beginners

1. Introduction: scram is simply a workflow you can use to create and maintain any product. The more complicated the product is, the more useful you'll find scum today. Scram is based on agile project management. But don't worry if you don't know what that is, because we'll touch on that in the first lesson. This class is for absolute beginners, so you don't need any prior knowledge. I've tried to keep things as simple as possible on All you need to do is become familiar with the terminology and workflow. I'm Ashleigh Bell and I'm a certified project manager in both agile and traditional project management methodologies have worked with many major national and international organizations, and now I'm really excited about sharing knowledge with you. So let's get started with less than one. 2. Scrum Basics Lesson 1: In this first lesson, you're going to learn about scrum on a little bit about agile on where it comes from. So let's get started. Okay, So let's start by talking about what scrum is. Scrum is a popular, agile framework. It's probably the most popular, agile framework at the moment on. One of the reasons for that is that it's so easy to understand, so it has a very simple workflow. On the flip side of that, it said that it's difficult to master, but I think by taking this course, you've taken the first steps towards mastering scram. It's great because it's very product focused, so it's You can use it in a project context to develop a product, but you can also use it in a B. A. U. Business is usual context to maintain a product that's been developed, so it's quite versatile. It's also focused on delivering value, so it's focused on delivering value as quickly as we can to the customer. Now let's take a quick look at what agile actually is. So Joe is basically just a way of performing work based on certain values, principles and practices. For the purposes of this class. We're really only going to be looking at project management, but it can be applied to any area. So let's take a look at the history Agile originated from the late 19 fifties through iterated software development on the key word here, really? Is it relative? This is fundamental to what we do in Agile. We're gonna come back to that. Later in the nineties, we saw the creation and development of various lightweight software development frameworks and methodologies. One of those it's scrum on It all kind of culminated in early 2000 with the creation off the agile manifesto that the agile manifesto was 17 software developers coming together on documented therefore values for a Joe on. This is at the heart of what jollies today. So they said that they value individuals and interactions over processes and tolls. They value working software over comprehensive documentation. They value collaboration over contract negotiation, and they value responding to change over following a plan. Now it's not to say that the things on the right aren't important. It's just to say that we value the things of the left more so that's at the heart of what our jollies Let's take a look, then at the what we call it curative approach. So at the top of the slide here, we've got the predictive approach, which is where you try and plan everything at the beginning and you don't deliver until the very end. Okay, so this is basically time going across here and you deliver something at the end. The problem with this is when you go to deliver, the market might have changed. And so what you're delivering might not be a value anymore. The requirements might not have been understood. So you're delivering something to the customer that they don't really want. And you, you might have to go back and re work in do more project work. So this is one style. This is the kind of traditional waterfall style. Then we've got our agile hit curative approach. So in this case, what we do is we perform a piece of work based on the requirements we have. We present it to the customer, we get their feet back from there, we course correct on. We take the feedback from the customer, build on what we've already produced on this continues. Basically, until we reached the end on, we've delivered what the customer wants, but the advantage here is that we're constantly delivering. We're delivering value on we're adapting to the customer's requirements, so that's really what agile project management is about. 3. Scrum Basics Lesson 2: in this lesson, we're going to look at who's who in scrum on what their roles up. So let's make the team in scrum. There were three Rolls, the product owner, the development team and the scrum master. Now let's take a look at each of those in a little more detail. The product owner owns the relationship with the customer. They're responsible for delivering value to the customer on for gathering and documenting the customer's requirements. Next up we have the development team. This is the role that's actually responsible for doing the work and developing the product . The development team is a self managed team, meaning that when they commit toe work, they decide how best to do it. Unlike the other roles the development team are made up of. A group Scrum states that for maximum efficiency, the group should contain between three and nine members and finally we have the scrum master rope. The scrum master is known as the servant leader of the team. They're responsible for facilitating meetings, removing obstacles, problem solving and coaching the team on scrum as well as other agile practices. So to sum up in scrum, we have three rolls the product owner, the Development team on the Scrum Master, the product owner and the scrum master. Both individuals on the development team normally consists of between three and nine developers for maximum efficiency. 4. Scrum Basics Lesson 3: Now we're going to take a look at the basic concept of scrum and the general work flow. The core component of the scrum workflow is called a sprint. A sprint is just a period of time when we take the requirements and develop something. Spring is normally presented as an arrow pointing from right to left, which represents the start and finish in the spring. The arrow which leaps back over the top, represents the actual doing of the work during the spring, a sprint so normally between one and four weeks in length. You can think of this as representing one week. So what happens is we start this print here we do one week's worth of work two weeks worth of work, however long the sprint is three weeks worth of work, four weeks worth of work and then finish the sprint sprints run back to back with no time in between. On there's no limit to the number of springs we can run. So in theory, if you're using scrum to maintain the product, this could go on for the entire life of the product. So what we can see here is we've got three sprints So basically we do this one that finishes. There's no time in between. This one starts that finishes the next one starts. And it could, as I say, go on forever. In addition to the sprint cycle, we also have the conveniently named scrum. This is just a 15 minute meeting which happens every 24 hours. It's an opportunity for the development team to align plan their work for the next 24 hours on a call out Anything which is blocking their progress. See, Conceive, the scrum is up here. So this basically represents one day. So before we were saying this represents week this represent today. So every day we have asked for a meeting. Okay, so this work pattern is basically one of the most iconic Andi recognizable symbols of agile . I'm just gonna talk you through it now look from start to end. So the sprint starts here, Remember, this is a week. So at our week starts on, we have at 1st 24 hours, period. So we have a scrum meeting and we have 24 hours. Scrum mated. 24 hours. It's grown meeting 24 hours. See, this goes on for five days and then our week finishes and then it all happens again. One to 34 five on again just went along. Your sprint is Once you've reached the end of the sprint, we get to hear and everything starts over again. We get around 24 hours, 24 hours, 24 hours and we're having a scrum meeting every 24 hours and again it carries on. So this could go on indefinitely if you're using Scrum to maintain something that is that in business as usual state or eventually it would reach an end if you're developing a product or developing anything and using script. So now we understand the scrum work pattern. Let's go ahead and look at the next level of detail. If we're going to be running a spring to develop something, then we need a way to input the requirements. This all starts with the perfect backlog, which is basically just a list of everything we can think off that we need to develop. It's prioritised with the most valuable requirements of the top at the start of every sprint. The development team pullers many of the requirements is they believe they can complete for that spring from the top of the product backlog into the Sprint backlog. And it's prioritized in the same way. This work basically just becomes the work which needs to be completed during the spring. At the end of spring, we need to output something. This is called a potentially releasable product increments, which basically just means anything from a minimum viable product to a feature on Huntsman . So let's look at the workflow here. So we've got a product backlog A to start here so you can see this Prioritize the green ones here at the bottom under is important, the ones at the top. So at the start off every sprint, we take items from the top of the product backlog and we put them into the sprint back look , and we prioritizing in the same way once this has been agreed, the sprint starts. So we start at cycle, which we sell before we've got a 24 hour Ask Rome mating 24 hours grow meeting and so on. And then this obviously goes around as many times as it needs to, and then eventually we output. Our potentially releasable product increments so I hope that's been useful to you. I hope that's helped you understand the basic workflow off scrum on In the next lesson, we're gonna go into even more detail. 5. Scrum Basics Lesson 4: in this lesson. We're going to bring the scrum workflow to life as we dive into the key events which take place during sprints and identify who is involved in them. Assuming this is our first print, some preliminary requirements gathering would have taken place between the product owner and the customer. These requirements would have been entered into our product backlog. The Sprint will start with Sprint planning meeting during this requirement, Support from the product backlog into the sprint backlog involved in the Sprint planning is the entire scrum team. The product owner, this grand master underdevelopment ing The team will also sat sprint go. The purpose of this is to create a feeling of coherence in the team. So was each member of the development team works on their own tasks They still understand and feel like they're working towards a common objective. The development work will take place as described in the previous lessons on a potentially releasable product feature or enhancement will be delivered. At the very end of the sprint will be the Sprint Review meeting. This is when the scrum team present their work to the customer in exchange for feedback. The feedback received may result in the product backlog being updated with new work or a change to the prioritization. Involved in the Sprint Review is the entire scrum team, this grand master, the development team, the product owner as well as the customer. This is followed by the Sprint retrospective, which is an opportunity for the team to review their own processes on plan improvements for the next print involved in the Sprint retrospective is the entire scrum Teen, the products owner, the scrum master on the development team. And finally, this leads us back to the sprint planning meeting, where changes identified in the retrospective are applied and then the cycle continues for as many sprinters are required. One final thing to be aware off after the product backlog is populated for the first time through the requirements gathering session, the product backup will still need to be maintained effectively. The requirements gathering is replaced by something called backlog grooming. This is when the product owner and the development team meet to reassess the product backlog items and make sure the work is well understood and ready for development. It could then be added to the sprint backlog during the next Sprint planning meeting. Backlog. Grooming is organized by the product owner and can happen at any time during a sprint. So that's it. Now you've got an understanding of the scrum workflow, So let's wrap things up in the next lesson. 6. Scrum Basics Lesson 5: in this class, you've gained a basic overview of scrum, the scrum workflow. Now it's time to put what you've learned into practice, download the printable template of the scrum workflow and correctly labeled blanks. I've also attached in answers sheep, which, additionally, could be used as a handy reference guide. Doing is the best way of learning, so you must give it a try. And for extra credit, you should also read the Scrum Guide, which is the official 19 page guide to Scrum. It's available to download free from scrum Dog. Having taken this course will really help you make sense of it the first time you read it. As there are little to no visuals to guard you, I've approached the creation of this course in an agile way and I'll certainly be iterating based on your feedback. So please let me know if you have any suggestions for improvement or additional areas you'd like me to cover, even if it's on a totally different project management topic. If you did enjoy this course, then please leave positive feedback. Thank you and I look forward to teaching you in future classes and tutorials 7. Bonus - An agile way to manage your own work: Hi, everyone. Welcome back. I just wanted to produce a piece of bonus content for you based on some feedback that I've had. I also just wanted to take this opportunity to say thanks to everyone who's watched thescore um, basics course that I produced already. I've had a good review. Some really good feedback on bond. I really appreciate it. So this piece of bonus content is something that I felt would help you give you a better idea of how you would how you could use scrum and agile yourself, even if you don't have a project team. But you got some kind of piece of work with some kind of project on that you want to do. So What I'm gonna do is based this on a piece of feedback that we had from Mohammed hair. So he was just asking for and some kind of agile or scrum in action course, and we actually see scrum at being used live in the team. So that's a great better feedback. Thanks very much. He's put posted that I put up there on the community. So if anyone's got any questions or something, that they want more information on. Definitely posted up because I'm more than happy to produce something to help you. So this is gonna be me doing this by myself. I don't have a team s, so it's gonna be more agile than scrum. Um, but I'm definitely gonna be using the scrum methodology that you've you've already learned . So if we think about what we've learned in the scrum basics, the first thing that you need to do for an agile or scrum project is create a backlog. So I'm gonna use trailer here, t manage the work. This is a really great tool. It's a free told you can just go to trail, oh dot com and sign up and you'll be able to do everything that I'm doing here. So the first thing I'm going to do is create a list called back. Look, Andi, if you remember everything that we need to do needs to be listed in the back. Look, so I'm just gonna list out a few things here off the top of my head. So the first thing I I'm definitely gonna have to do some filming, So let's add that in there as ah, a card. So this is a list. And within the list, we can add cards. And the list can be as long as you like. So filming it, Stephanie One thing. I'm definitely gonna need an example. Project. I'm gonna have to come up with that. Um, I'm gonna have Teoh do some editing. At some point. I'm probably going to need to do a voice over as well. Uh, I am going. Teoh. Need to find some actors, your friends who are willing to participate. Um, I'm also going to need Teoh design a lesson plan, um, filming design the lesson plan editing. Um, I'm also another thing we're definitely going to need to do is research, um, video production companies. Because I don't think I'm gonna have the ability if I'm gonna be in these videos as well. I guess my role in the video is gonna kind of be the scrum. Master is what I'm thinking. So I'm definitely going to need someone else to do the filming for me. So research video production companies. So I think that's plenty to get started. Now, if you remember back to the scrum basics, we list everything in the back log on to get started. We only need as much. We only need as much information in the backlog as is possible to get a started on the project. Another thing that we need to do is organize the scrum backlog. Sorry. Organized the backlog. Um, in order of priority. So let's look at this. So filming is gonna come later? Definitely. Um, I'm definitely gonna have to come up with an example. Project editing. Stephanie gonna come after filming Czar Provisional filming there. Voice over is gonna come off or is part of editing. Um, finding actors is gonna come before filming. Designing a lesson plan is definitely gonna be at the top. Um, research production companies. Yeah. I'm definitely gonna have to do that somewhere up here. So what I've done now, it's just organized these cards in order off what's most important to me? It the top and what can be done later at the bottom. The next thing I'm gonna need to do is I'm gonna need to create a sprint backlog. So if you remember, we create a backlog and the backlogs gonna grow over time as well as we learn more. And as I've got time to add more things in here and think about this a bit more. Um, the sprint backlog is everything we can do or we think we can do during the spring. So as well, let's create another list for what's actually being done. So let's say Sprint in progress on I'm going to just put a reminder in here for me as well . I'm gonna say, for the purposes of this project, I'm going to say Sprint is one week. I'm just gonna put that they're so reminder, I'm gonna do a final list. I'm just gonna call that completed, okay? And that's enough for now. So the next thing I'm gonna do is I'm gonna say that my sprints run from Monday to Friday on a Monday, I'm gonna come in here and I can do it now. It doesn't matter, but I'm gonna come in here. I'm going to pull into the sprint backlog everything that I think I can do in one week because my sprint duration is gonna be one week. So definitely I can come up with an example project. Definitely. I can design a lesson plan, but that's gonna take a bit more time than the knee example project. So I'm not gonna commit to anything else, because I think that's plenty for me to get done in one week on top of my day job as well. So that's plenty. Then on Monday, when I start this project on to come in here and I'm going to start working on one of these , So the thing that I'm gonna work on is definitely let's say it's Monday. Now I come in, I'm definitely gonna come up with an example Project that's gonna be the first thing that I want to do. So I want some kind of theme around my course. So I'm gonna work on that the way that I'm going to do this. Now each of these cards, physical cards and the boxes that they're in is called a list. Some people call them, call it a bucket, which is fine. Um, but you can go into much more detail in these as well. So if I click on that brings up, this can look a bit confusing in the beginning. But every one of them has a description. You can add comments if you do have a team that you're working with you can add other members here is well s so that they can collaborate with you and they get updates when something changes on the card and there's loads of benefits doing this. So what I'm gonna do is for my example, projects. I'm gonna come in here and I'm I'm gonna right in here what my projects is gonna be about on. Then I'm gonna click, save and close this and that will be updated. So I'm just gonna just right example. But now click. Save on when I close this your noticed. This little icon has appeared here, so that's just a visual indicator that there's some details in that cart now. So assuming that I've come up with my idea for a project, I'm gonna move that to complete it, and I'm going to drag in here, designed a lesson plan. So I know that that's what I'm working on. A really good way of working here. What will I like this way is to use a checklist. If you've got a list of items you can you can list them down in the description if you want . But I kind of like this so I'm gonna call this one lessons you can have as many as this hopes lessons. You can have as many of these checklists as well as you want as well. So I'm just gonna for this example, I'm just gonna say lesson one. Lesson two lesson three on and so on. So this is just a way of me kind of doing, like, instead of bullet points. I'm I'm doing these checked boxes. And instead of lesson, one lesson to us and three, I'm gonna actually come up with, like, a subject for that lesson or kind of key learning points that I want that video to be about . So these are actually gonna be the individual videos in the class. Okay, so now that I've done that, come back here and you can see this one's got a little check mark icon as well. And 03 So there's three check check box site items in there. Um, so presuming that I've come up with all my lessons, I'm gonna move that to complete. So by this stage, it's going to be like Thursday for idea in the week, I'm gonna finish my sprint. Um, obviously, in, um, scrum we talked about a retrospective on we talked about a review meeting. I'm just working by myself. It so I don't need to do that. I've done these, have completed them on as you complete these other things are gonna come up that you realize that you're gonna need to do on my list pretty short here. So I might create a separate card in my backlog for each lesson that I'm gonna do so I can detail what needs to be done and how it's gonna be filmed on. That's that's fine. I might lose. I might get rid of filming then and have these in favor of these kind of individual cards. Um, and then I can drag those cards. So let's just do an example here, so I'm gonna say lesson one lesson to, uh, etcetera so I could move those up here, and I could get rid of this card. Now, I think I just need to click, uh, archive. Yeah, and then I can delete it. Okay, so I've got those there now instead of what was there before. So I'm going to drag what I could do once thes get to the top of the list. I'm ready to film those lessons. Maybe you've got Maybe they can only film one lesson a week. Maybe that's the way it's gonna work out. In that case, I'll just put, you know, this filming I could rename this filming lesson one, Um, and in there I can have all the details of what that lesson is gonna be. A bow I can have. He's gonna be involved. I can just basically you can use this in any way you want. It's really versatile. And once I start on that drug, it here I might have beamed to film, too. So in that case, I'll be doing that one. See, on Monday cheese, they'll come in. Maybe that's gonna take you dont Thursday a drug that in there and then I can just drag them off here as they're completed. So this is the way that I would work, that I'm going toe work for creating that that video and I just thought would be a really interesting thing for you to see, to give you an idea of how you can apply agile to the work that you that you're doing in the projects that you're doing so. Hope that's been helpful. Andi, I look forward to teaching you in the next class. Thanks a lot. Bye.