7-9 minutes<\/p>\n
A sprint planning meeting is conducted before the start of a sprint . The purpose of this meeting is to determine the sprint plan and set a sprint goal .<\/p>\n
Sprint planning includes agreeing on the number of backlog items in the sprint that is the responsibility of the development team and as well as to define the goal for the current sprint and sprint backlog .<\/p>\n
During the sprint planning meeting, the product owner describes the highest priority features to the entire team. They will then discuss which stories the team will do in that sprint. The meeting should be attended by the whole team. If additional expertise on specific backlog items are required, then stakeholders can be also invited. The team may include the refinement sessions as well.<\/p>\n
Sprint planning<\/p>\n
Below are some of the benefits of running a successful Sprint Planning meeting:<\/p>\n
Enables the Team to agree on the sprint goal and commitment.<\/p>\n
Enables task discovery, sign up, prioritization and estimation<\/p>\n
Creates the platform to communicate dependencies and identify team capacity to set and commit to an achievable sprint goal.<\/p>\n
Each sprint begins with a sprint planning meeting. Typically, for a four-week sprint this meeting should last eight hours. For a two-week sprint, plan for about four hours. As a general rule of thumb, multiply the number of weeks in your sprint by two hours to gety our total sprint planning meeting length. The following table illustrates the rule.<\/p>\n
1 week 2 hours<\/p>\n
2 week 4 hours<\/p>\n
3 week 6 hours<\/p>\n
4 week 8 hours<\/p>\n
Now, let\u2019s review what we need to prepare for each of the scrum roles before we attend the Sprint Planning Meeting:<\/p>\n