What Happens During Sprint Planning?

 

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.

 

Who Makes Decisions?

As we already said, the whole Scrum team should be involved in sprint planning, and everyone has a specific role:

  • Product owner should propose the sprint goal and the backlog items to be worked on in the upcoming sprint. 
  • Developers should give estimates on how many tasks they can handle in the upcoming sprint and discuss how they’re planning to deliver these tasks and ultimately achieve the sprint goal. 
  • Scrum Master facilitates the communication between the team members and ensures that the discussion is effective. He or she needs to make sure everyone is on the same page regarding the goal and the backlog items that will be handled in the sprint. 

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.

 

How to Plan a Scrum Sprint in Infinity

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:

  • Step 1: Move the task from Backlog to Current Sprint folder.
  • Step 2: Once you move a task from the Backlog, you will already have some fields filled out - name, description, assignee and type. You can update them if necessary.
  • Step 3: Add a time estimate that you will get from the developer responsible for the task.
  • Step 4: Add 'To Do' status which will move the task to the first column. 
  • Step 5: Add a priority level - High, Medium or Low.
  • Step 6: Add a due date.
  • Step 7: Add a feature reference to link the task to the corresponding feature from the roadmap. 
  • Step 8: Add any relevant links if necessary.
Share This Guide With Your Friends
Build Groundbreaking Products With This Framework
Fast-track your product creation process
Keep your teams always in-sync
Improve time management and work effectiveness