Sprint planning is an event in Scrum that defines what can be deliver in the next Sprint and how that work will be accomplish.

In this article, Dave West, CEO of Scrum.org, describes the sprint planning ceremony as described on Scrum.org. Scrum.org teaches Scrum according to the Scrum Guide, which is consider the official guide for the Scrum framework in the agile world. Below, Atlassian’s Megan Cook shares her take on in this video:

What Is Sprint Planning?

Sprint planning is an occasion in Scrum that begins the Sprint. The purpose of dash planning is to define what may be supply in the Sprint and the way that work could be executed.

In hand-to-hand combat, the Sprint is a set period of time in which all the work is done. However, before you can take action, you need to set up Sprint. You must decide the duration of the time zone, the goal of the Sprint, and where you will start. The  session starts the Sprint by setting the agenda and goal.

  • The what: The product owner describes the sprint goal (or goal) and what elements of the backlog contribute to that goal. The Scrum team also decides what can be done in the next Sprint and what they will do during the Sprint to make this happen.
  • The How: The development team plans the work necessary to achieve the sprint goal. Ultimately, the resulting sprint plan is a negotiation between the development team and the product owner based on value and effort.
  • Who: You can’t plan a sprint without the product owner or development team. The product owner sets the goal based on the value he seeks. The development team must understand how they can or cannot achieve this goal. If any of the events are missing, sprint planning is next to impossible.
  • Inputs – A great starting point for your iteration plan is the product backlog, as it provides a list of “tips” that could be part of the current iteration. The team should also review the existing work done on the increment and have a vision of the capacity.
  • The Results – The most important outcome of the sprint planning meeting is that the team can describe the sprint goal and how they will start working toward that goal. This becomes visible in the sprint backlog.

Preparing For The Sprint Planning Meeting

Hosting a large  event takes a bit of discipline. The product owner needs to be prepare, combining the lessons from the previous sprint review, stakeholder feedback, and product vision to set the stage for the Sprint. For greater transparency, the product portfolio must be update and refined for clarity. Refinement of the backlog is an optional event in Scrum, as some backlogs do not need it. However, for most teams. It is best to bring the team together to review and refine the pending work before  the Sprint.

Set A Time Limit For Sprint Planning

Sprint planning should not be limit to more than two sprint hours per week. So, as an example, the sprint making plans meeting for a -week sprint could closing no extra than two hours. It is a timebox. Or setting a maximum time for the team to complete a task, in this case planning the Sprint. The scrum is a master is responsible for ensuring that the meeting takes place within the allotted time. If the team is satisfy before the deadline, then the event is over. A timebox is a maximum time allow; no minimum time allows.