A Sprint Planning Meeting Agenda Template You Can Use Right Away

Meeting GuidelinesAn inside look at the meeting ground rules used internally by Fellow.app, the top-rated meeting productivity software company. ResourcesBlogLeadership, productivity, and meeting insights to fast-track your way to being a great leader. Browser ExtensionsAccess meeting notes inside of Google Meet and get helpful details through Google Calendar events.

• However, for this post, we only consider the simpler case when we have one development team dedicated to one product.
• The Oxford Dictionary defines “refinement” as the improvement or clarification of something by the making of small changes.
• Near-term items need to be fully fleshed out before they are labeled as such.
• This includes engineers, QAs, and designers, each of whom is critical to the sprint planning process.
• The process is fully collaborative, and shorter times between meetings allow every team member to get on the same page.
• This sprint goal defines what your team is trying to accomplish during the sprint and will give your developers direction.
• Have your meeting summary generated in a matter of seconds using Adam the AI assistant.

After checking your developers’ availability, you can determine which product backlog items to include. After all, most sprint planning meetings go on for over an hour, so it’s not unusual https://www.globalcloudteam.com/ for concentration to drop. Then, draw up the meeting notesat the start of your sprint planning meeting, and search for keywords such as accomplishment, improve, different, etc.

What is a Sprint Planning Meeting?

Instead of building the most complete, “every minute of the sprint is accounted for” sprint plan, focus on the goal and build enough of a sprint backlog to get started. Next, ensure that the product backlog is ordered to allow the team to pick up work if they delivered on the sprint goal early. Running a great sprint sprint planning agenda planning event requires a bit of discipline. The product owner must be prepared, combining the lessons from the previous sprint review, stakeholder feedback, and vision for the product, so they set the scene for the sprint. For transparency, the product backlog should be up-to-date and refined to provide clarity.

Once you’ve gone over the previous sprint, it’s best to convey new information about the project immediately. If, by any chance, the transcript reveals that the previous sprint didn’t go particularly well, it’s essential to maintain a positive attitude and not dwell on the setbacks. There are many templates out there online but we like this free one from Docket.

Re-prioritize and assign tasks/tickets for this sprint? (30 minutes)

Since sprint planning is always time-boxed, we included this sprint planning meeting agenda you can use, with suggested times beside each section. A sprint review meeting focuses on examining the actual work (tickets completed, bugs resolved, etc.) that was completed during the sprint with the aim of updating the backlog. A sprint retrospective, meanwhile, is focused on improving the team’s performance and ways of working together. The development team reads through each piece of work (i.e., user story) and evaluates its complexity.

You can also begin the meeting with an icebreaker activity to get everyone in the mood to discuss and communicate openly. If the answer to any of these questions is no, consider whether the work is truly ready for development. In some cases, a “no” may be unavoidable (e.g., a last-minute bug that should be addressed but hasn’t been scoped yet), but this usually isn’t the case.

Sprint Review Meetings

Brennan McEachran is the CEO and Co-Founder of Hypercontext, a suite of tools to help leaders and their teams streamline objectives, meetings and morale into one workflow. He has spent more than a decade in the leadership and employee engagement space building apps to create better relationships between managers and their teams. Imagine that you have ten team members who work eight hours per day. However, you also know that everyone attends an hour-long meeting twice a week. That means that each team member loses two hours per week, totaling 16 hours across the entire team. Good estimation requires a trust-based environment where information is given freely, and assumptions are discussed in the pursuit of learning and improvement.

In addition, some user stories come from older sprints because they were not completed previously. Bringing all of these things together helps form a specific sprint goal. With all these things in mind, let’s put together a sprint planning meeting agenda.

Sprint Planning: Ziele & Teilnehmer des Meetings

The product owner identifies and prioritizes what represents meaningful work and why it’s meaningful. Consequently, the development team evaluates and actually picks the work for the upcoming sprint. There is a high chance that since the last time the team planned a sprint, any of the team members may have received updates from outside stakeholders.

You should plan for these scenarios to avoid overcommitting to complicated work. The best way to do this is to account for these unknowns ahead of time when estimating stories during your grooming ceremony. For example, let’s say you’re hoping to fit in a three-point and five-point story, but there’s only capacity left for five points. You can decide to pull in the five-pointer or opt for the three-pointer with another small story. Engineers define implementation complexity and how much work it can commit to. Just because a story is dev-complete doesn’t mean it can be released; there needs to be testing capacity too.

What is a sprint review?

LinearB may send you email occasionally about how you can optimize productivity. For more tips on how to best plan for a sprint, check out this post.

Backlog refinement is an optional event in scrum, because some backlogs don’t need it. However, for most teams, it’s better to get the team together to review and refine the backlog prior to sprint planning. The product owner begins the meeting by sharing the product goal and explaining what the scrum team aimed to accomplish during the sprint.

✅ Do a quick wrap-up and create your action items

It’s best if this is stated clearly to the whole team to avoid unrealistic assumptions. To start the current sprint, you need to go over what happened in the previous sprint. Then, confirm with the team any issues that are specific to the last sprint and record them. Review the story points and record what was done and what needs to move to the backlog again or be considered for the next sprint. Ask the team for their feedback on what needs to be changed in the next sprint.