Sprint Planning
Sprint Planning is a Scrum event that is held before the start of the sprint to establish the scope and priorities of the coming sprint. Its purpose is for the whole team to establish an agreed sprint goal based on the Product Owner’s view of the value that can be created for the customer. To establish a scope of backlog items that can be got to done. For each backlog item the team decides how done will be achieved.
In A Nutshell
The Scrum Guide provides more detail on the Sprint Planning event and how it should be performed. The Product Owner and the Scrum Team must be present in Sprint Planning. Other stakeholders can be included to provide advice and guidance.
To keep the Sprint Planning event to a reasonable duration, experience has shown that the Product Owner and the Scrum Team should be fully prepared. In particular the backlog items that are going to be considered for inclusion in the sprint must be considered to be ready for work by the team. By undertaking Product Backlog Refinement on these items, the Product Owner, the team and other stakeholders will have sufficient understanding of the items to discuss their inclusion.
Related Practices
Teams plan work to fill their short-term planning horizon. With a clear understanding of current priorities and the capacity of the team, work items are chosen to satisfy the forthcoming delivery goals. The team elaborates the plan as necessary to ensure that there is a shared understanding of the work that is required.
Related Articles
Relative estimation is a simple concept, but one that causes all sorts of problems for new teams and for experienced agile practitioners. This article examines some of the reasons behind the confusion and suggests a new, clearer way of thinking about the process of relative estimation. This new pattern makes a very clear break from more traditional estimating techniques.