What Is A Sprint Planning Meeting Agenda?

The sprint planning meeting agenda

In a Scrum project, the Sprint planning meeting agenda is one of the most important activities undertaken by the team. The product owner plays an important part in the agenda. In Scrum, out of the many important duties carried out by a PO, a very important one is to create the product backlog based upon the vision of the stakeholders, and subsequently maintain or “groom” it with the help of team members (preferably). However, once the backlog is created and all required product backlog items are properly defined in it, it becomes necessary to “prepare” for the next step in the Agile product development cycle – plan and develop effective sprints so shippable user stories are delivered at the end of sprint cycles. Offering consistent development over successive sprint iterations is an inherent feature of Agile Scrum. In a sprint planning agenda, the objective of a sprint meeting is to prepare productive sprints so the team can develop meaningful stories.

So, what does a sprint planning meeting actually consist of? In practice, the meeting is conducted in two parts – the first part is dominated by the product owner while in the second part the development team actually prepares tasks from user stories taken up for development in the sprint backlog.

scrum tool | sprint planning meeting

Sprint Planning Meeting Agenda

First part of sprint planning

The product owner is the most “conversant” person as far as user stories are concerned since he or she actually “creates” the product backlog. The stories need to be explained to the team members. During the first part of the Scrum sprint planning meeting, the PO selects some of the most important product backlog items from the top of the backlog, and creates a “sprint backlog” by transferring the selected stories into it. So, the sprint backlog is a subset of the main backlog, and contains a “chunk” of stories which carry high business values. The PO explains how the development of a particular story should be carried out by the development team. The acceptance criteria is explained and the team is briefed regarding what it should do to ensure their “development” is shippable i.e. the stories are bug free and satisfy the benchmarks or acceptance criteria linked with each story. The PO also answers any doubts or queries put up by the team.

The first part is attended by the entire team – the product owner, scrum master, and the development team members. It is not necessary for the stakeholders and project owners to attend the meeting, but if they desire to do so, they can attend the meeting as “passive” invitees, and not disturb the proceedings with their suggestions or even try to get “involved” in the meeting.

Second part of sprint planning

User stories form the base of all development activity in Scrum. The entire product is developed by creating shippable stories, which are later integrated to “form” the complete product. During the second part of the Scrum planning meeting, the team starts discussing how it will … Read more>>>

About mrugeshpanchal

Mrugesh Panchal works as a director in Bharti Consulting Services SARL, a leading solutions provider company having its headquarters in Clichy, France and operations center in Vadodara, Gujarat – India. The company has several subsidiaries – Bharti Soft Tech Pvt. Ltd which offers development and consultancy services catering to the I.T. market, and Bharti Nutritions Pvt. Ltd. which offers health products. Mrugesh is a co-founder of the QuickScrum Tool, a powerful, easy to use, and versatile web based application centered on Scrum methodology. The product is developed and marketed by Bharti Soft Tech Pvt. Ltd, which is a Bharti Consulting Services SARL undertaking. The QuickScrum Tool is an agile, dynamic, easy to use, project management tool which incorporates scrum methodology. To know more about the scrum tool please visit http://www.quickscrum.com.
This entry was posted in Agile, Agile Scrum, Agile Scrum model, Scrum, Scrum Agile, Scrum Agile process, Scrum Framework, Scrum Methodology, Scrum process, scrum tool, sprint, sprint backlog, sprint backlog items, Sprint Planning Meeting and tagged , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s