Fellow.app Fellow is the meeting productivity and team management software where teams gather to build collaborative agendas, record decisions, and keep each other accountable. Slack IntegrationCollaborate on meeting agendas, share notes, and exchange feedback – without leaving Slack. Sales LeadersFellow helps Sales leaders run productive 1-on-1s, team meetings, forecasting calls, and coaching sessions. However, since it’s also unrealistic to expect your team to be 100% productive the entire time they work, you can’t go by this ideal number. Instead, you’ll need to estimate how productive they are on average. If you believe they are 90% productive, then multiply your ideal capacity by 0.90.
Go around the room and have each person share an update on work that wasn’t completed the past sprint and why. Whether it’s scope creep or lack of resources, starting your meeting off with this agenda item will ensure that you’re always working to improve how the team works. It’s also critical information for planning your next sprint because you’ll have a better understanding of your team’s bandwidth and how much new work you can assign. 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. The What – The product owner describes the objective of the sprint and what backlog items contribute to that goal.
Who participates in sprint planning?
You should initially set your sprint planning team meetings for 1 hour with your team. If you prepare and share an agenda in advance you’re likely to get through more faster. Having recurring planning meetings helps with strategic alignment, making sure that each feature or user story relates to the overall product vision and roadmap. Additionally, planning sessions boost team accountability and morale.
List the topics to be discussed in the meeting as agenda topics. First, specify the background of the meeting by entering the date, time, location of the meeting. The total number of story points per sprint equals team velocity. Let’s say your team is 10 people and they work on the project 5 days a week 4 hours each day. It allows us to qualify and clarify the user stories that we are intending to work on. Dropping the big tasks down into smaller ones, identifying dependencies, – all that makes us more aware of the actual job.
A Sprint Planning Meeting Agenda Template You Can Use Right Away
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. The general rule of thumb is that the duration of a sprint review per week should not exceed one hour. There are many templates out there online but we like this free one from Docket. Use it to review goals, define your scope and make decisions collaboratively. Break down large projects into manageable tasks and milestones across sprints.
Team Meetings GuideLearn how the world’s best companies run effective team meetings – featuring insights from Figma, Buffer, Close, Webflow, Shopify, and more. If you estimated user stories using a numerical scale, you can get a rough idea by adding up several tasks until you get close to your capacity. sprint planning meeting agenda Just make sure to leave a bit of wiggle room — after all, this is just an estimate. After determining your team’s overall capacity, identify how many tasks your team can take on and how quickly it can complete them. Again,oth your estimates and your notes regarding past performance can help here.
What Is the Sprint Planning Meeting?
Knowing your team’s capacity for the work they can commit to is critical for successful planning. This should not be based solely on past sprint velocity because each sprint https://www.globalcloudteam.com/ is different. Sprint planning meeting are usually full-day events for a month’s sprints but can be proportionately shorter for shorter sprints managed by a scrum master.
- The product owner defines the goal based on the value that they seek.
- “We plan a dream sprint where we get everything done,” he says.
- They should provide the scrum team sufficient information to perform the activities required to complete and test the user stories within the allowed timeframe.
- List the topics to be discussed in the meeting as agenda topics.
Most teams prefer to get together to review the backlog prior to the sprint planning meeting. 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. Team capacity is the measure of how many story points or product backlog items (scrum parlance for “tasks”) your team can complete during a sprint under normal circumstances. Capacity is calculated as the number of team members multiplied by how many hours a day they can work productively. As described above, a lot goes into leading successful sprint planning meetings.
The Sprint Planning Meeting Agenda
However, before you can leap into action you have to set up the sprint. You need to decide on how long the time box is going to be, the sprint goal, and where you’re going to start. The sprint planning session kicks off the sprint by setting the agenda and focus.
Start the agenda with a review of the last sprint, and then communicate any new developments that occurred in the meantime. Given this long period, you want to ensure your developers understand what they’re trying to accomplish and what the objectives are. With this feature, you’ll have a clear, measured outlook on your employees’ priorities and can easily reach a fair consensuson the sprint goal.
Step 3. Present team velocity
The benefit of this technique is that it’s very universal and globally understood, making it fit for international teams. Once you’ve planned out the sprint, give everyone one more chance to address any issues or concerns before finalizing the work. With a clear understanding of the current state of your team let’s move into what we need to do next sprint. If you don’t have Goals/OKRs, use our free library of over 360 goal and OKR examples to be inspired — Including OKRs for 18 specific engineering roles and 4 product roles. 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.
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. 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. During the sprint planning meeting, the user stories, which are approved and estimated are taken up for discussion by the scrum team.
Long-term projects / epics check in (Quick scoring 🟢🟡🔴 5 minutes)
The best practice is to schedule the sprint planning in the weekly planner online at the beginning of the week so that the flow is not interrupted by the weekend. Have your team share what was completed last sprint Celebrate progress. Connect and re-connect their work to the bigger picture studies have clearly shown that understanding the signifigance of a task increases performance.