The scrum team, including the product owner, scrum master, and developers, attends the sprint planning meeting. Here are the definitions and responsibilities of each role as quoted from The Scrum Guide. The article also includes a free sprint planning meeting agenda template and a detailed explanation of each agenda item. In the scrum framework, the scrum master, product owner, and the entire scrum team attend the sprint planning meeting. You can invite outside stakeholders — but that usually doesn’t happen often. One of the most important responsibilities of product owners and scrum masters is the sprint planning meeting.
GuidanceGuidance allows admins to suggest talking points for managers to discuss during their 1-on-1s. StreamsStreams are digital notepads to help you organize projects, share OKRs, and whatever else you dream up. Every issue that pops up should be recorded with an action item that identifies who’s going to follow up and by when . At the end of the meeting, make sure that your team members understand what they’re tasked with and that there are no known blockers that could slow down their efforts.
Sprint Review Meetings
The stakeholders will have a chance to interact with the product while also providing feedback. It’s crucial to include stakeholders as part of the sprint process. This makes stakeholders feel involved and more likely to understand the path the product is taking during development.
Here, we’ll cover how to create a sprint planning meeting agenda that will ensure your project is moving in the right direction on the right timeline. In the sprint planning meeting, you’ll comb through the product backlog, decide on action items, define a sprint goal, and dive into multiple user stories. The focus of the sprint planning meeting is to set and agree upon the sprint goal–the amount of work the team believes it can complete during the sprint.
Sprint planning meeting agenda: what does it look like?
On-Demand DemosEmpower your team to build a culture of productive meetings with these on-demand product tutorials. Team Meetings GuideLearn how the world’s best companies run effective team meetings – featuring insights from Figma, Buffer, Close, Webflow, Shopify, and more. Jira IntegrationTurn action items generated in Fellow into Jira issues so their completion status stays in sync between both tools.
All of this should be decided collaboratively in order to ensure the whole team is on the same page regarding how much work is required for each backlog item. The Inputs – A great starting point for the sprint plan is the product backlog as it provides a list of ‘stuff’ that could potentially be part of the current sprint. The team should also look at the existing work done in the increment and have a view to capacity. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team. The process is all about prioritization, so you’ll want your team on the same page regarding what’s essential and what can wait, which is sometimes difficult for teams to accomplish.
An agenda for effective sprint planning meetings
It’s important to go over any new information from the market or customers that helps to set the context for the upcoming sprint. If the team is new and doesn’t have an established velocity, it’s best if the product owner doesn’t suggest a sprint forecast. Instead, the first sprint should be an exercise for the whole time. Forecasting the pace at which the team works is a trial-and-error process. In this process, at the first sprint, the team will use its best judgment regarding predicting velocity, and after a few sprints, good estimates will be obtained. They identify the product mission, the product roadmap, and a release plan with the highest-priority features launching first.
A good sprint planning agenda template will help you stay on track, but you have to address the sections in the template before everyone sits down to meet, whether in person or virtual. The template is there to prepare you and guide you through the meeting. It would be best to consider deadlines when you’re prepping for a sprint planning meeting, as some projects have them and others do not.
The new sprint has just started
Now, with Otter AI Chat, OtterPilot provides real-time conversational question and answer support, and generates meeting-specific insight and content. Unlike in sport, scrum encourages you to be always sprinting so you can deliver working software, while continuously learning and improving. With end of support for our Server products fast approaching, create a winning plan for your Cloud migration with the Atlassian Migration Program. Use this Sprint Planning Meeting and Agenda Template to host a collaborative discussion that allows the Scrum team to choose the direction for the next sprint. It helps developers solve reported issues in their app faster, without having to bother the user. Product Owners tend to have the most communication with stakeholders, so they should be particularly adept at clarifying acceptance criteria and product requirements.
- This shouldn’t be a challenge, as you’ve likely already hosted a sprint retrospectivethat addressed these topics.
- 1) Sprint goal and roadmap – The Scrum Master starts the meeting by proposing sprint goals and placing them in the context of the product roadmap.
- In this post, we’ll be exploring the basic building blocks of a sprint planning meeting agenda.
- Sprint planning is reliant on a refined backlog and backlog refinement gets the highest-priority work into the next sprint.
- One-on-One MeetingsHave engaging 1-on-1s, never forget what was discussed, and build better relationships with your direct reports.
If the team doesn’t know where to go and how to get there, meeting customer needs will be difficult. 3) Velocity – Velocity metrics capture the team’s ability to deliver value to customers in the form of completed and delivered user stories. The Scrum Master provides the team with a target velocity for the current sprint, which must be agreed on with the rest of the team. During the demos, the stakeholders attending the sprint review meeting assess the presentations against the original sprint goal and provide any feedback they may have. The demos are evaluated on whether or not they meet the users’ needs, create value, account for internal dependencies, and improve functionality. It is common for a product that was presented to go through multiple development iterations based on the feedback from sprint stakeholders.
Best practices for running a successful sprint review
Tasks that are backlogged often become the focus for future sprints, and are moved to a sprint planning meeting agenda. The best sprint planning meetings blend strategic alignment with tactical planning. When sprint planning is done well, team members leave the meeting feeling motivated and excited about the work ahead. Attendees of sprint review meetings commonly include the scrum team and scrum master, development team, product owner, designers, writers, and analysts. The scrum master is tasked with facilitating each sprint review meeting and making sure the participants understand the purpose of the event. The preparation of the sprint planning meeting falls mostly on the shoulder of the product owner.
Getting each backlog item in step 3 ready consists of the following sub-steps. Creating a culture of recognition means giving space for your team to recognize each other. Create known space for people to share kudos for sprint planning agenda their teammates — for many, peer-to-peer feedback is more meaningful. How to use Range A quick start guide for taking your team productiv… There is no difference between backlog grooming and backlog refinement.
What’s the difference between a sprint review and a sprint retrospective?
ProductFeatures OverviewSee how high-performing teams are using Fellow to level-up their meeting and productivity habits. Sprint planning shouldn’t take up more than two hours for each week that the upcoming sprint is expected to last. So, for the typical two-week sprint, the planning session should https://www.globalcloudteam.com/ run four hours. For example, if a story feels like it’s probably three points, it’s a good idea to overestimate the time it will take to account for unforeseen issues. When faced with a scenario like this example, you should discuss the business, user, and technical tradeoffs with the team.