• Product Owner

This is the perfect Sprint Planning

One of the most powerful principles of Scrum is working in short sprints. A project is broken up into short time periods. Scrum has a total of four meetings, four meetings along the way. The first meeting is the Sprint Planning. Here the sprint goal is created and described how the Scrum team will achieve this goal.

Each new sprint is started with a Sprint Planning meeting. This is the Scrum meeting at the beginning of each sprint. This is where the goal of the sprint is put together so that the Scrum Team can work with complete focus.

Every Scrum process we differentiate into several sprints. Each sprint consists of four Scrum meetings, namely: Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. In this article, we are going to talk about the perfect Sprint Planning.

Ideal Preparation Sprint Planning

The Product Owner, on the other hand, prepares by making the Product Backlog completely up-to-date and, most importantly, insightful. This means, for example, that the Product Backlog Items for the next 2 Sprints are clearly worked out so that about 5 to 10 items fit into the Sprint. Product Backlog Items in the form of a User Story are “ready”: they also include an estimate of effort and acceptance criteria.

Developers prepare by going through the ready items. They’ve come across these in previous refinement sessions, so this goes nice and fast.

The Scrum Master facilitates Sprint Planning. He or she ensures that Product Owner and Development Team understand each other well and come to a draven planning for the sprint in the set timebox.

Here we go … your Sprint Planning

Scrum Master: he or she makes sure everyone sticks to the timebox. This is set prior to the Sprint Planning. A 4-week Sprint implies a maximum timebox of 8 hours.

Product Owner: he or she submits the highest priority Product Backlog Items to the Development Team during Sprint Planning. The Product Owner explains them so it is understandable to everyone.

Developers: the developers determine how many items to pick up. The list of selected Product Backlog Items forms the Sprint Backlog. The Scrum Team collectively sets a goal that shows what should be completed by the end of the sprint.

Enough items selected? Good. Then the Developers make a plan to do the work. It is broken down into small tasks no larger than 1 day’s work. These tasks are posted on the Scrum board under the heading “To-Do… And off they go!