Articles, Blog

Sprint Planning Meeting Explained | Know all about Sprint Planning Meeting

November 17, 2019

Hello and welcome to knowledgeHut. In this video, we will be talking about the
Sprint Planning Meeting in Scrum. So let us begin. The Sprint Planning Meeting is one of the
four ceremonies conducted in Scrum, the other three being-
The Daily Scrum The Sprint Review
And the Sprint Retrospective The start of the Sprint planning meeting is
officially the start of the Sprint. This meeting is held with the objective of
selecting the set of Product Backlog items which are to be delivered during the current
Sprint. It is attended by the Product Owner, the Scrum
Master, and the entire Scrum Team. Although the team can also invite other Stakeholders
to attend the meeting, this rarely happens in any company. The Sprint Planning Meeting mainly focuses
on two things- First, what is to be built during the Sprint? And second, how the team will build it? For deciding what is to be built, the Product
Owner presents a rough idea of the goal to the team. The Product Owner tells about the features
he/she wants to be added or to be improved in the product. The initial goal presented by the Product
Owner helps in the selection of the Product Backlog items to be built in the current Sprint. The Product Owner then presents the highest
priority items from the Product Backlog to the team. The team members then ask questions to the
Product Owner so that they can get a clear picture of what exactly is to be created. Then comes the second part of the Sprint Planning
Meeting where the team tries to figure out how to build what they have decided to build. This can be done in whichever way it is helpful
for the team. Sometimes, the work required to be done to
complete the product backlogs is broken down to rough task-lists, sometimes only the first
few items are broken down into tasks and sometimes it is not done at all. Breaking the backlogs into tasks also helps
in confirming whether the right amount of work is selected or not. As the Agile values suggest, team members
should remember and accept the fact that situations, conditions, and requirements can and will
change during the course of the Sprint. Therefore they should not be expected to create
a perfect Sprint Plan, they should put just enough efforts in planning that they are roughly
confirmed that they have selected the right set of the Product Backlog items. The official timebox for Sprint Planning Meeting
is 2 hours per week, which means for a 2-week long Sprint, it is 4 hours and for a four-week
long Sprint, it is 8 hours. Generally, it is seen that teams require even
lesser time than the official allotment. After the how and what part of the meeting
is completed, the Scrum team along with the Product owner revisit the Sprint Goal and
decide whether any changes are required to be made in it based on the outcomes of the
Sprint Planning Meeting. So this was all about the Sprint Planning
Meeting. We hope that you understood the concept with
the help of our video. Please don’t forget to hit the like button
and subscribe to our channel to keep upgrading your knowledge.

You Might Also Like


  • Reply Earl Norman February 4, 2019 at 8:24 pm

    FYI: You have a spelling error at 2:16.

  • Reply Rich Imbrogno April 11, 2019 at 4:41 pm

    Just starting in Scrum and watching many videos and reviewing many links. This is really tight and concise. Thanks for releasing this.

  • Leave a Reply