Avoid changing the sprint goal midway through the meeting — it’ll take away from the focus the team needs to achieve its commitments. It’s not uncommon for issues and roadblocks to emerge during the planning meeting. That’s why you should set some time aside in each planning session to discuss them with your team. Sprint planning is easier with tools like Vowel – you can use it to take notes together, collaborate on meeting agendas, and make sure the next steps are clear by assigning action items. Meeting agendas help to keep any team meeting on track by outlining the topics, tasks, and decisions that will be discussed (ideally with times for each).

• Secondly, the scrum master brings forth any time limitations for the upcoming sprint, like vacations and holidays.
• The team decides on user stories according to priority and their capacity and velocity.
• They’re short and move super fast so teams can get a lot done in less time.
• To define a solid sprint goal, make sure to include previous sprints’ goals, guidelines, and any other resource your team will need to define an efficient sprint goal.
• Having clear priorities aligned with customers’ needs ensures that development efforts focus on the most meaningful work.
• Since sprint planning is always time-boxed, we included this sprint planning meeting agenda you can use, with suggested times beside each section.
• That acts as a motivating factor and encourages the team to act faster on their work.

The team should consider ways to reduce technical debt with each sprint. The “tech debt” quick filter uses the JQL “type in (bug)” to limit the view to bugs. Just extend the JQL query to include additional issue types as needed. If the team is new and doesn’t have an established velocity, the product owner shouldn’t suggest a sprint forecast. Instead, this should be an all-team exercise because it’s important to have buy-in from each member.

LogRocket generates product insights that lead to meaningful action

To make proper estimations, teams use t-shirt sizes, the Fibonacci sequence, or planning poker. So, when the team checks stories, they need to break them up so that a story fits in one sprint to complete. The natural language processing preparation of the sprint planning meeting falls mostly on the shoulder of the product owner. The scrum team, including the product owner, scrum master, and developers, attends the sprint planning meeting.

For me, the biggest change has been the naturalness of the responses these models generate to a broad array of questions or prompts, across industries and languages. From our perspective, what this means is that we can now distil long call transcripts into readable summaries and key points just like notes a person might have taken. For an end user this is a game changer – let’s face it, someone rarely has time to read a full transcript, they are mostly interested in just a few key moments. This perspective led us to develop Moments as a powerful way to deliver practical insights from business conversations. As our first Moment, we found Complaints have significance to a range of organisations seeking to improve how they serve their customers.

What is sprint planning? Guide and meeting agenda cheat sheet

Notebooks can help you visualize what these discussions are all about. Of course, it also offers a simple way to start organizing and prioritizing work in your own sprint planning sessions. This is when the team collectively commits to the batch of work for each sprint, which is typically two to four weeks long.

Any notes you and your team make during the meeting are time-stamped too, so you’ll always be able to go back and get the full context from the recording. 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. MindManager helps boost collaboration and productivity among remote and hybrid teams to achieve better results, faster. Use the agenda to help everyone move through the various topics of discussion without getting bogged down trying to identify and estimate every possible task. The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog.

How to run quarterly planning meetings [with agenda]

The product owner and product manager (program manager) collaborate to write the user story. However, according to each team’s needs, it can be held every one to four weeks. In my role it’s important to stay at the forefront of this ever-evolving landscape.

A good sprint plan motivates everyone by defining an outcome and a clear plan for success. 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. 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.

What do you do during sprint planning?

At this point in the meeting, the team should be comfortable with the sprint forecast. At the end of sprint planning it’s good practice to get verbal approval from everyone in the room about what the team is actually committing to shipping at the end of the sprint. Also, establish that each team member has at least one task to start on and nobody is duplicating work. At the start of the meeting, the scrum master presents any relevant action items from the team’s retrospective. Next, the product owner give product or market updates so everyone is on the same page and has the broader context fresh in their minds. If not, identify the amount of effort left on any stories or tasks that are rolling over.

The Transformer neural network architecture underlying current language models was proposed back in 2017, and models have been steadily growing in capacity since then. Another big step forward in this field was around 2018 when automatic speech-to-text reached human-level accuracy at transcribing conversations. Q1 FY24 Highlights
● Revenue of $9.8m in Q1 FY24 up 10% on Q4 FY23 and 46% on Q1 FY23. ● Net operating cash outflows including finance lease repayments1 of $8.2m in Q1
FY24, down 3% from Q4 FY23 and down 20% on pcp.

Set Dependencies

Your sprint planning agenda will guide the meeting, ensuring that team members are focused on the most important aspects of sprint planning. The objective of a sprint planning meeting is to discuss and reach consensus on what items to work on as part of the next sprint. It should cover the size of two sprints, so the product owner can efficiently answer the team’s questions. So, a sprint backlog is a list of all the tasks (features) you need to accomplish to have the final product or, in other words, complete the project. Now that your team understands their velocity, you’re ready to plan your team’s capacity. Then review each team member’s capacity as you plan and prioritize sprint tasks and goals.

It’s a good idea to keep these documents in one centralized place that every team member can easily reach. It’s also important to make a distinction between the sprint goal and the sprint backlog. The sprint goal is the objective of the sprint such as a hypothesis to test, an experiment to implement, or a general goal to achieve. The sprint backlog is the work that needs to be done for the team to achieve the goal. The primary purpose of sprint planning is to decide what needs to be done and who will be doing it. BUT the meeting offers benefits beyond just dividing work among team members.

Agenda of a Sprint Planning Meeting

You will determine what you will build, test, and release to customers. Team engagement and morale will naturally fluctuate from sprint to sprint. These variations often show up during sprint planning, but resist the temptation to dig into it right then and there. Instead, use the team’s retrospective to understand any issues that are impacting morale. Teams that respond quickly to culture and development concerns are happier, more productive, and write better code. During sprint planning, it’s easy to move stories in and out of the sprint as the team creates its sprint forecast.

Engineering meetings

The best way to do this is to account for these unknowns ahead of time when estimating stories during your grooming ceremony. 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. The team members have the opportunity to select the task they are comfortable handling and the one they have expertise in. It gives them the morale to produce the best since they are the ones who selected what they are good in.

Leave time to discuss potential issues

If you treat velocity as something that needs to improve, your team will intentionally give higher story points to the user stories. It’s essential to keep in mind that you don’t decide on the sprint goal alone, despite being the team lead. Instead, it should be a team effort, with each developer giving their own opinion. You and your developers are ultimately working toward creating a functioning product, and the product backlog serves as a list of tasks to help you accomplish that goal. Use these meeting minutes to summarize the final meetings of your previous sprint, and you’ll have a sprint review ready-made. The product owner will be successful when the development team has understood the product’s vision and how the coming sprint advances this vision.