In this lesson, I'm going to go over a high level overview on Scrum lifecycle. We're going to go through the details of each one of these. But before we get into it, I wanted to give you provide you a high level picture of the major processes that happen in Scrum. So we start with a product backlog. And part of that is like your requirements document. So it has the requirements of all the requirements that are relevant to the product in the form of what are called stories and we don't worry about what stories are, we're going to be going through them in one of the future lessons.
Once you have that product backlog. You create sprints, sprints, meaning iterations, multiple iterations for that, to develop that product. For each before you begin each sprint or each iteration, you pull the requirement that aren't going to be built in that sprint into what is called a sprint backlog. So you have your sprint requirements, you're going to begin your sprint, each sprint is two to four weeks long, typically two weeks long. Every day, you're going to have a scrum meeting. And we go through what is called meeting has, etc.
Like I said in a future lesson. And then at the end of the sprint, you would have a potentially shippable product. So that's kind of a high level lifecycle of Scrum. And next, I'm going to go through, you know, show you a video that would be kind of a more of an animated version of what I kind of went through, which probably kind of covers it well, better than I just did. So with that, let me get this started. complex projects could lead to real headaches, organizing the team, changes in scope, roles that aren't clear But you can change that with Scrum and agile framework.
At its foundation. Scrum can be applied to any project or product development effort. Here's how it works. A product owner creates the product backlog, a prioritized wish list. During sprint planning, the team pulls a chunk from the top of that list and decides how to complete it. The team has a set timeframe.
The sprint to complete their work. They meet in a daily Scrum to keep the work moving forward. Along the way the scrum master keeps the team focused at the end of the sprint, the work should be potentially shippable. The team conducts a sprint review on the product and a retrospective on the process. Then they choose the next chunk of the backlog and the cycle repeats. With Scrum you can ensure the most valuable work has been committed By the time the project ends, tackle your projects with Scrum.