Sprint Planning

1. Goals

The third process step for Application Development is sprint planning. The whole development team plans the work that will be done (scope) for the current sprint at this meeting. The team agrees on the sprint objective at this meeting, which is enabled by the scrum master. The goal of this action is to use the information from the product backlog in order to create tasks that can be included in the sprint execution. There are different methods that the team is using for sprint planning. The important part here is that this is a continuous process step that starts over again after every sprint.

1. Scope

Working instruction covers enterprise application employees in Europe.

1. Responsibility

• Product Owner: Participates in the task sizing and creating the sprint backlog.

• Manager: He can be involved in the sprint planning process. Also, he can assign people to a certain task from the sprint backlog.

• Scrum Development Team: Shares domain knowledge and it can participate in the task definition and task sizing steps.

• Scrum Master: Participates in all steps from the sprint planning.

1. Process

In Scrum, sprint planning marks the beginning of the sprint. Sprint planning's goal is to specify what can be completed in a sprint and how it will be done. The whole scrum team collaborates on sprint planning. The sprint is an established time frame in the scrum where all work is completed. However, you must prepare for the sprint before you can take immediate action. The length of the time box, the sprint objective, and the starting location must all be determined. The sprint planning meeting establishes the focus and agenda for the sprint.