Sprint planning happens during the sprint planning meeting held by the whole Scrum team - the product owner, Scrum Master and the development team.
As its name suggests, sprint planning is the process of planning the following sprint. The meeting shouldn’t take more than eight hours for a month-long sprint, but ideally, it should take an hour per each week of the sprint.
The plan should be the result of a collaborative discussion of the entire Scrum team and it should identify the backlog items that will be delivered in the upcoming sprint and determine how this work will be done.
Sprint planning needs to happen right before the sprint but after the sprint review and retrospective.
Each successful sprint needs to have a sprint goal, which is the main priority at the beginning of every sprint planning meeting. The sprint goal is the objective of the sprint that should guide the development team while building the next product increment and all the tasks for the following sprint should be aligned with the sprint goal.
As we already said, the whole Scrum team should be involved in sprint planning, and everyone has a specific role:
Together, they should decide which items from the backlog will be completed in the sprint, as well as define their requirements, potential problems and the factors that will determine when a task has been done.
Planning the sprint in Infinity can happen during the sprint planning meeting. As the team discusses the tasks that will be done in the next sprint, the product owner should move tasks from Backlog to Sprint folder using drag and drop and hitting ‘Move’ button.
Once a task is moved to the Sprint, product owner needs to add all the necessary details to define the task, such as the team member who will be responsible for this task, estimated time to do the task, flexible due date, priority, etc. Here are all the steps you need to make: