Sprint

Welcome to another video with the Agile Shop. In this video, we'll answer, backlog may represent many months of work which is more than a scr To determine the most important subset of product backlog items to build the next sprint, the team holds the sprint planning. The roles that join the sprint planning meeting are the product area. The creation of the user story is the main responsibility of the product owner. The user stories should be estimated by the development team in story points. If you want to know more how user stories should be structured with acceptance criteria or what are story points, please watch our other videos here. The collection of user stories that are picked from the product backlog to go into the next sprint forms the sprint backlog. Usually, the product owner would explain one story at a time to the development team. The entire team will have a conversation to make sure everyone on the team understands the user stories. After the user story is understood, the development team will drive the conversation on how this user story will be achieved. At the end of this conversation, the development team will estimate the user story in story points and introduce the user story in the sprint backlog. This process repeats until the development team has enough user stories to fill a sprint backlog and know more that they can complete sprint planning meeting depends on the length of the sprint. If the team allocation of user story, the sprint planning meeting should be anywhere from 2 to 4 hours planning how many user stories the scr The sprint planning meeting is usually scheduled on Monday or midweek. If you want to know when you should schedule your sprint planning and all the other scr This ends our video on what is sprint planning in scr Make sure you subscribe to our channel for future content.