Acceptance criteria describe what success looks like for this backlog item from a business point of view. A helpful question when trying to define them is “How will we demonstrate this user story to stakeholders? Don’t confuse these with your definition of done, which describe when any backlog item is considered done from a team perspective.
- This gives the team time and space to dig into the acceptance criteria and fully understand the effort without the added pressure of figuring it out immediately.
- You can also use the template to record and follow up on any potential risk.
- On-Demand DemosEmpower your team to build a culture of productive meetings with these on-demand product tutorials.
- Engineers define implementation complexity and how much work it can commit to.
- Now, let’s get into the specifics of what happens during an effective sprint planning meeting.
This can also surface tradeoffs related to complexities or dependencies, which may need to be evaluated before estimating or committing to the work. 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. If you treat velocity as something that needs to improve, your team will intentionally give higher story points to the user stories. You and https://www.globalcloudteam.com/ 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. The most effective method for communicating information is in person—which is precisely why you should bring it up during the sprint planning meeting. Use these meeting minutesto summarize the final meetings of your previous sprint, and you’ll have a sprint review ready-made.
Epics to be Delivered
Defining the sprint goal brings clarity to team members as well as project stakeholders. The sprint goal also helps identify which items from the backlog to add to the sprint. Now, let’s get into the specifics of what happens during an effective sprint planning meeting. With a properly groomed product backlog it’s time to actually start planning your next sprint. Before a sprint gets underway, you need to know what you’re trying to accomplish and how you’re going to get there.
What you have to do is to list the tasks for each of these user stories. The product owner presents the context for the work considered for the next sprint. The product owner explains where the user stories sprint planning meeting agenda 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.
How to run a sprint planning meeting
Jira is the #1 software development tool used by agile teams. Jira Software is built for every member of your software team to plan, track, and release great software. As a team, decide what you’re going to accomplish over the course of the sprint.
The last step is for the stakeholders to evaluate the sprint goal and provide their feedback. The first step to sprint planning is to know what you want to achieve – in the next 6 months, in a year and so on. The purpose of estimating velocity is to develop a new velocity for every sprint. Looking back at past sprints will help reflect on objectives, outcomes and effectiveness, and set realistic expectations for the upcoming sprint. This article is the second in a series on agile ceremonies. So let’s walk through four tenets of sprint planning we find most helpful.
Review the last sprint
This informs the timeline for the sprint, which should be flexible and able to accommodate changes based on new information or modified requirements. The availability of team members to handle the workload is known as its capacity. The team’s capacity is informed by who is available to work on the sprint and the amount of time they can devote to the sprint goal. Agile systems rely on work cycles known as iterations or sprints that break projects down into smaller, more manageable chunks. A sprint is a fixed length of time in which specific work tasks must be completed. The Scrum Guide identifies a maximum of 8 hours for a month long sprint.
Going through this process for every ticket is also a great way to keep everyone vigilant about taking into account every part of a ticket. People often forget about code review, for example, or they don’t assign enough time for it. But estimating every ticket as a group encourages them to think the ticket through from start to finish. Slack Set up meetings, add agenda items, and get meeting reminders directly from your Slack community.
Sprint Retro Meeting
Include links to velocity reports and other relevant documents to the template. This helps your team understand each member’s contributions and how much work they can complete during the sprint. Having planned out your user stories, your next step is discussing the velocity of the upcoming sprint. Often overlooked is adjustments and changes to team capacity and availability.
If you’re in tune with your team’s work and typical velocity, your wish list should be pretty close to the actual result, but don’t be frustrated if the stars don’t all align. The backlog grooming ceremony is a much better time to scope and estimate stories before they’re pulled into a sprint. This gives the team time and space to dig into the acceptance criteria and fully understand the effort without the added pressure of figuring it out immediately.
Products
Excel at project management and be loved by your teammates. This will help team members to feel motivated in what they’re doing and will encourage them to take responsibility for their work. Ideally, you would have one sprint goal per sprint, ensuring that everyone is on the same page and working towards the same outcome. Sprint meetings are designed to answer any and every question that team members have on their minds. In cases where teams try to avoid Scrum specific language, this event may be called iteration planning.
An agenda is a priceless asset when organizing your sprint planning meeting, as it ensures you don’t forget to address any important points. For most, company and team goals are set on a quarterly or annual basis. As a team, you’re likely working on big features or campaigns. Along with many other benefits, sprint planning allows the team to break these bigger projects into smaller, more manageable chunks of work.
Work Management
Team Meetings GuideLearn how the world’s best companies run effective team meetings – featuring insights from Figma, Buffer, Close, Webflow, Shopify, and more. Slack IntegrationCollaborate on meeting agendas, share notes, and exchange feedback – without leaving Slack. Fellow for EnterpriseSupport company leaders with Fellow’s uniform meeting templates, collaborative one-on-one meetings, and feedback tools. ProductFeatures OverviewSee how high-performing teams are using Fellow to level-up their meeting and productivity habits. Finally, select the user stories involved in creating the deliverable. You have to click on the … button to select the User Stories in a popup window.