[Agile & Scrum] Sprint Planning Flashcards
Sprint Planning
Start of any Scrum or Sprint Cycle. The main goal is to move user stories from the product backlog to the sprint backlog,
for each user story we choose, we need to determine a set of things to be confirmed into the sprint. So this set of things include the acceptance critiria, as well as prioirties of each user story that we choose, and the effort that is going to be estimated for each user story.
Setting up the sprint planning meeting. lettign the team know that we are starting a sprint planning and reminding everybody that we have a time box to keep to, which in this case is two hours.
the product owner will write the sprint goal, which we need to establish before the start of the session. so that everybody has a god idea of what user stories to choose that are important for this sprint. Once everybody is clear about the sprint goal, the developers will now choose the proper user stories on the cards, to be moved from the product backlog into the sprint backlog
While they are doing that, the developers also need to confirm two things with the product owner. first, the priority value, second the effort estimation in terms of story points. So once each of the user stories are chosen and placed into the sprint backlog. one of the key tasks that the product owner has to do is to create a set of acceptance critiria.
Po and developers work together to decide whether the acceptance critiria is appropriated for each one of the user stories. this is import because at this sprint planning stage team are supposed to agree on what it means for each user stories to be completed. So once everybody agrees upon the acceptance criteria for each one of the user stories, now the developers have the role of creating sub-stories base on these acceptance critiria as well as the description of these user stories,
the reason first to determine the deasibility of these cards, based on the detailed development tasks that’s supposed to be done from the develoeprs’ perspective. and then aslo possibly break up larger user stories in case they are too big for a day of development. Then the last thing is also to faciclitate effort estimation, because once you have all the sub-tasks created, then you have a better sense of how much needs to be done for each one of the user stories.
