What Is The Purpose Of Sprint Planning Meeting In Agile?

She is now making a shift from business to psychology and bridging her knowledge from both domains, as she pursues a Graduate degree in psychology at Trinity College, Dublin. Kate is fascinated about how our physical environments influence our thoughts, behaviours, actions and wellbeing. She is a certified yoga teacher, a passionate writer and traveller. One-on-One GuideThe Art of the One-on-One Meeting is the definitive guide to the most powerful tool for managers. PodcastSupermanagers is for managers, like you, who want to be extraordinary at the fine craft of management. Cross-Functional MeetingsStay aligned on projects, drive progress and accountability, and improve collaboration.

purpose of sprint planning meeting

The Story Points estimates that the teams make, however, are not always carried out during the Sprint Planning event. If the scores for success are high, the Scrum Master role thanks everyone for the active participation and closes the Sprint Planning meeting. Planning Poker is not practiced by all Scrum teams, as this “game” can take a long time, and the team may experience inconvenience and distress over time. Time estimation can also be accomplished through faster group discussions by the Development team. Keep in mind that this approach is just a popular technique for estimating development time. Sometimes the difference may be due to a misunderstanding of a User Story.

Length Of Sprint Planning Meeting

The discussion serves to identify problems, opportunities, and solutions. Anyone can take part in the topic if there is something to add and to help find the right solution. Otherwise, the discussion may go beyond a reasonable time frame.

Because sprint planning can be so painful we discuss backlog items at a surface level, avoid difficult conversations, and rush to finish and get back to “work.” The product owner presents the context for the work considered for the next sprint. The product owner explains where the user stories come from, such as customer requests, customer support, or the marketing department. The scrum master will be successful when the development team has understood the limitations for the coming sprint. The product owner will be successful when the development team has understood the product’s vision and how the coming sprint advances this vision.

What Is The Purpose Of Sprint Planning Meeting In Agile?

Moving forward, the scrum team would know that, on average, they complete 30 story points per sprint and could use this as a guide when going through the backlog items in sprint planning. Before the actual meeting, make sure that your product owner has prepared all the items in the backlog. This task takes a significant amount of time and the output is really important to plan a successful sprint. The product purpose of sprint planning meeting owner should understand the details on each item so that they can explain or clarify any questions that the rest of the team might bring up. The Sprint Planning Meeting is a meeting that is used to plan the work that will be completed during the next sprint. The product owner will present the product backlog to the team and the team will select the items that they believe they can complete in the next sprint.

  • Backlog refinement is an optional event in scrum, because some backlogs don’t need it.
  • Have you ever sat in a sprint planning meeting that seems to drag on and ultimately doesn’t result in anything much—except for dread of the next one?
  • The product owner defines the goal based on the value that they seek.
  • Moving forward, the scrum team would know that, on average, they complete 30 story points per sprint and could use this as a guide when going through the backlog items in sprint planning.
  • As you go through each item in the backlog, the team will need to discuss and ask questions.
  • The team decides how much gets done during a sprint, not an overpowering Product Owner or an outside stakeholder.

The Product Owner role is not allowed to make any changes or modifications to the Sprint Backlog. If the Product Owner role has a strong need to add or remove an item for some reason, he or she should approach the Scrum Master role and explain its concerns and needs. The Scrum Master role will convey the desire of the Product Owner role to the Development team. If the Development Team agrees, the needs of the Product Owner role can be met. After arranging the Sprint Backlog list and creating separate tasks for each item, it is strongly recommended that no one else adds or removes Product Backlog Items in that list. Only the Development Team is allowed to manage their Sprint Backlog.

The Scrum Framework

The best sprint planning meetings blend strategic alignment with tactical planning. They are times for development teams to not only assign work, but also come together around a shared vision for what the work means and how it will impact the business and your customers. When sprint planning is done well, team members leave the meeting feeling motivated and excited about the work ahead.

Estimate the timeframes for each of the tasks assigned and agree on what “done” will look like for each item. With the advancing design, development, technical, and business knowledge, the BVOP™ Product Manager is a master role and decision-maker for the products. The BVOP™ Director is the most advanced and important role inside Agile products and services-based organizations. The different teams have many variations of estimating the time it takes to develop the Product Backlog Items.

For example, leaving things vague is much worse than describing something as a question to be answered during the sprint. The sprint goal describes the objective of the sprint at a high level, but the backlog Items can also be written with an outcome in mind. User stories are one great way of describing the work from a customer point of view. User stories, written like the one below, re-focus defects, issues, and improvements on the outcome the customer is seeking rather than the observed problem. During the Sprint Planning Meeting, the Scrum Team builds a viable Sprint Backlog, which determines the user stories and tasks the team is going to implement until the end of this Sprint .

The team will have a better idea of this the longer they work together. Before we get into the steps of this meeting, some preliminary work needs to get done. Arguably the most important part of a sprint planning meeting is the preparation that must be done before the meeting starts. Velocity will ebb and flow over time, but a mature agile team’s velocity will start to trend upward as they get more and more used to working together and on the product. Velocity is a key number for the Product Owner to keep in mind as they work to figure out how many sprints it will take to release the next version of the product. After going through this, you will be armed with more information to make a bigger impact in less time at the next sprint planning meeting that you run.

purpose of sprint planning meeting

The Planning Poker meeting aims to achieve independence among members of the Development Team and provokes the idea that anyone can throw their card without worrying about the rest. No one should throw their card after the Development team has already revealed the card numbers. It is assumed that both inexperienced and experienced teams might make inaccurate estimates at the very beginning of the project or often make mistakes in their analysis and planning.

New Products From Point A

It does not have to be hard, even if the problem you are solving is. The Product Owner introduces the Sprint goal and her preselection of requirements, which should go into the product increment. These user stories are edited and broken into smaller user stories when necessary so that they can be processed within one Sprint. The team needs to take vacations, public holidays, time spent on Scrum Rituals, and a small contingency for unforeseen issues into account to propose a reasonable capacity.

A sprint represents a specific amount of work that can be completed in a given amount of time. The sprint planning meeting aims to allow the development team to identify, estimate, and include meaningful work in an upcoming sprint. In this post, we’ll be exploring the basic building blocks of a sprint planning meeting agenda. Saving the best for last, we’ll leave you with a sprint planning meeting template so that you can try the method to see if it works for you and your team. Sprint planning can become ineffective when your team does not have a properly refined product backlog from which to draw product backlog items. In scrum, the sprint is a set period of time where all the work is done.

purpose of sprint planning meeting

Make sure you have a meeting agenda to send out to your team. Scroll down to save our sprint planning meeting template so that you can test it out yourself. The Scrum Guide identifies a maximum of 8 hours for a month long sprint. Many teams that follow a two week sprint are able to effectively complete both parts of sprint planning within 1 – 2 hours. The team members determine how many of the product backlog items they forecast they will be able to complete and determine how they will deliver those product backlog items. Typically, for a four-week sprint this meeting should last eight hours.

We empower organizations to build the right things by growing product leadership in the heart of a company. The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment. However, enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint.

How Many Product Backlog Items Should Be Estimated?

They also benefit from better alignment with others by having the time to talk about how their work will fit together over the next sprint. In this article, I am going to unpack this particular meeting and offer up some helpful tips to make your next agile sprint planning meeting more efficient, effective, and less dreadful. The sprint goal can be used for quick reporting to those outside the sprint.

The goal of HOW-Meeting is to fill the Sprint Backlog by identifying the concrete tasks needed to implement committed user stories for the Sprint. These tasks usually include activities such as analysis, design, development, testing, software build packaging, and documentation. The objective of sprint planning is to work out the key details regarding the team’s planned work during the next sprint. With that in mind, the sprint team should plan to address at least the following issues during this meeting. If anything else came up during sprint planning that wasn’t already on the radar, find a space to record those and identify action items.

OK, given that we understand the objective – the reason for running this Sprint – let’s come up with our current best idea of what to do, to get there. This commonly means we select backlog items that we best think will realize the value we’re after, helps us achieve the Sprint Goal. So we come up with a forecast of what we want to do, in order to achieve the outcome we’re investing in. Unlike in sport, scrum encourages you to be always sprinting so you can deliver working software, while continuously learning and improving. If the team is in their first project Sprint, it is advisable to “play” as many items as possible in a reasonable amount of time.

However, before each development sprint can start, the development team must understand the work and commit to completing it in the time allocated for the sprint. Now that we know who’s on the invite list for this kind of meeting, we can get into the purpose of running a sprint planning meeting and the value https://globalcloudteam.com/ that this session adds to your upcoming sprint. The event should occur after the sprint review and retrospective from the previous sprint so that any output from those discussions can be considered when planning for the new sprint. It does not have to occur immediately after those other two events.

Sprint planning can become costly when your team spends an inordinate amount of time planning compared to the act of delivering the product backlog items. Teams may find it helpful to establish a sprint goal and use that as the basis by which they determine which product backlog items they work on during that sprint. In Agile project management practices, there is also the term increment, where it is often called Program Increment. In a scaled Agile environment, Program Increment is a time concept designed to increase synchronization between all teams in the program or portfolio. The recommended PI length is five reps. A typical model is four iterations working on functions and one iteration for innovation and planning .

Purpose Of The Sprint Planning

So she can answer questions from the Scrum Team and bring clarifications for the requirements and their acceptance criteria. It is important to find a balance between people and organization’s needs. Scrum Master and Product Owner roles do not have regulated official participation in this technique. The Scrum Master role participates in its discretion without interfering with the team and can monitor transparency, respect for team members, and honesty. Often, new members of the Development Team are very distracted by this “game” and are afraid to throw their cards until they somehow understand what cards were thrown by senior team members. After the discussion, a re-play is performed, and each participant of the Development Team throws a card again.

Leave a Reply

Your email address will not be published. Required fields are marked *