In this lesson, I'm going to be going through what are called a scrambled scrambled, again is a tool. scrambled is also called an agile board or Kanban board. Basically, it's nothing more than basically, sticky posts are sticky posters or index cards that you can put on the wall or a whiteboard. You can also use an online application tools such as JIRA, what you do is is you and you'll see in the next slide, I have some examples but basically what you do is is your once you have your stories, or the sprint backlog stories, you basically put them in the the status of Neil, if you will, our to do and then what you have is a workflow. So you may Have to do in progress done on you can have some other workflows, you know it's not you can have multiple different workflows. You don't have to have a single workflow for every project.

We can pick what works for you. Some of the typical workflows are to do in progress done to do development, QA done, etc. As you'll see that basically again, in a scrum board, you have a product backlog that you start with, as you have seen before. From the product backlog, you get the sprint backlog. And from the sprint backlog, you get this thing which is assembled. In this particular Scrum board you have the word prop it starts with to do and then in progress and done.

So you start initially every all your stories are going to be in the to do status, and then as you pick a story to start working on It it's basically it goes in the in progress and then once the story is completed goes in the done status. This is basically typically put in a place where the whole team can see or if it's digital, you know the whole team has access to so they're working can see the progress of the sprint. And once all these stories are in the done status your all your sprint backlog is complete. Now, it's not unusual that you may not be able to get all your stories in the done status but the sprint time runs out. Still the sprint is complete you will just basically get credited for the number of stories that were all the way done. And the story which is partially done we'll start in the to do status again in the next sprint or whichever sprint is it is going to be the part of next.

Once this is done your sprint delivery This time. Here's an example of another similar Scrum board, if you will, which has slightly different workflow. Now in this case, you have the two Do you have dev you have QA and then you have done so you can see that basically, you know, in previously our stories were in the one and three storybooks, we're in the in progress status. Now you can divide it more between development, QA, etc. Basically depends what makes sense for your project. And you create that particular Scrum board for it and then you use it and then you know, once you your stories are done, then you have a sprint deliverable complete.

So that's a little bit about the scrum board, what it is and how it is used for again, this is to provide an easy visual representation, either physically on a whiteboard on the wall if the team is co located, or using a digital app. application which is typically more of the case more and more of the case these days, such as data or that everybody in the team has access to so they can basically see how the sprint is progressing.