What is included in a sprint planning meeting?
Table of Contents
What is included in a sprint planning meeting?
Every sprint planning meeting agenda should include discussions about the ultimate objective of the sprint and the team’s capacity, followed by a granular look at the sprint backlog, before you start slotting tasks into the sprint.
How do I write a sprint planning document?
How to use the sprint planning meeting template
- Close the previous meeting. Start your sprint planning meeting by following up on any open question from the previous sprint.
- Share sprint goals. As a team, decide what you’re going to accomplish over the course of the sprint.
- Present team velocity.
- Plan team capacity.
How do you plan a sprint planning meeting?
Best practices for running a sprint planning meeting
- Start with the big picture.
- Present new updates, feedback, and issue.
- Confirm team velocity and capacity.
- Go over backlog items.
- Determine task ownership.
- Confirm new issues, impacts, and dependencies.
- Reach a group consensus.
- Officially begin your sprint.
What are the two parts of the sprint planning meeting?
The sprint planning meeting consists of two parts. In the first part the product owner shares the sprint vision with the team and presents the backlog for the sprint. In the second part of the sprint planning event the team meets to discuss how the PBIs should be decomposed into developable tasks.
What should happen in sprint planning?
The plan should be the result of a collaborative discussion of the entire Scrum team and it should identify the backlog items that will be delivered in the upcoming sprint and determine how this work will be done. Sprint planning needs to happen right before the sprint but after the sprint review and retrospective.
What should not be considered during sprint planning?
3 Things to Stop Doing During Sprint Planning
- Resizing Carry-Over Product Backlog Items (PBIs) When work is carried over from one sprint to the next, teams often spend a lot of time trying to resize the PBI(s) to accommodate remaining work—but they shouldn’t.
- Assigning Tasks.
- Filling Up the Entire Capacity of the Team.
What is sprint planning template?
Sprint planning is an Agile ritual where the team plans which tasks will be completed in the next sprint. Use this template to review already-prioritized items in the backlog, estimate the capacity of your team for the upcoming sprint, and decide which items from the backlog will be worked on.
What should be done in sprint planning?
Sprint planning involves two key tasks: grooming the backlog and deciding which work to complete in the upcoming sprint. At Atlassian, we’ve found that backlog grooming is best done in a separate meeting with the product owner and scrum master before the actual sprint planning meeting.
What is done during sprint planning?
What is sprint planning? Sprint planning is an event in scrum that kicks off the sprint. 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.
What are the key activities done in sprint planning?
How many hours is sprint planning?
Sprint planning is limited to a maximum of eight hours. The general rule of thumb is to allow two hours of sprint planning for every one week of sprint length. That means teams should timebox sprint planning to four hours for a two-week sprint and eight hours for a one-month sprint.
What should scrum master do during sprint planning?
A scrum master or coach typically facilitates sprint planning in order to ensure that the discussion is effective and that there is agreement to the sprint goal and that the appropriate product backlog items are included in the sprint backlog.
Who facilitates the sprint planning meeting?
ScrumMaster
Sprint planning is a collaborative effort involving a ScrumMaster, who facilitates the meeting, a Product Owner, who clarifies the details of the product backlog items and their respective acceptance criteria, and the Entire Agile Team, who define the work and effort necessary to meet their sprint commitment.
Should a team assign work during sprint planning?
For newer scrum teams, assigning tasks during sprint planning acts as something of a safety net – it’s reassuring to know who’s responsible for which items, and assigning every task can help ease worries that stories will get left behind.
What are the two most important deliverables for a sprint planning meeting?
What should not be considered in sprint planning?
Can Scrum Master and Product Owner be the same person?
Can the Product Owner Also be Scrum Master? The short answer is no. The Scrum Master and Product Owner should always be separate roles, and there are few reasons why this is beneficial to your business. First, when Scrum Masters act as Product Owners, they don’t have the same access to customer feedback.
