| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 | Publish Date not found |  0 Views |
——–
Sprint planning initiates the sprint.
The purpose of sprint planning is to determine the work to be done in the sprint – the sprint backlog.
Who participates?
1) The entire Scrum Team works together to create an outcome plan.
2) The Product Owner ensures that participants are prepared to discuss the key Product Backlog items and their connection to the product goal.
3) The Scrum Team may also invite other people to participate in Sprint Planning to provide advice.
When does it take place? Sprint Planning is the first event of the sprint. To reduce complexity, it is ideally carried out at the same time and place.
Sprint planning is limited to a maximum of 8 hours for a one-month sprint. For shorter sprints, the event is usually shorter. – Scrum does not say whether for sprints that last less than a month, the maximum duration of the event should be proportionally shorter. There is no such thing as /"no more than 4 hours are required for a two-week sprint/".
The Scrum Master ensures that this event takes place, is positive and productive, and stays on time.
Sprint planning covers the following three topics:
1. Why is this sprint valuable?
2. What can be done in this sprint?
3. How will the chosen work be done?
In the first part, the Scrum Team answers the question, "Why is this Sprint valuable?" The Product Owner proposes how the product could increase its value and utility in the current Sprint. Then, the entire Scrum Team works together to define a Sprint Goal. The Sprint Goal is the only goal for the Sprint. It communicates to stakeholders why the Sprint is valuable. The Sprint Goal creates coherence and focus and encourages the Scrum Team to work together rather than on separate initiatives. The Sprint Goal must be set before the end of Sprint Planning. It is included in the Sprint Backlog.
In the second part, the Scrum Team answers the question: “What can be done in this Sprint?” Product Backlog items that can be “done” by the Scrum Team within a Sprint are considered “ready” for selection in a Sprint Planning event.
The developers select items from the Product Backlog and include them in the current Sprint. If necessary, they clarify the information with the Product Owner. The Scrum Team can refine items of the Product Backlog to increase understanding and trust.
The developers determine how much can be done within a sprint. Scrum does not specify a sizing method or a unit of measurement: days-hours, t-shirt sizes, story points – anything can be used. Both the unit of measurement and the evaluation method are chosen by the teams. This is an example of how self-management works.
Predicting how much can be done within a sprint is no easy task, but the more you know about your past performance, your future capacity, and your definition of “done,” the more confident you will be in your sprint forecasts.
Can the team select a Product Backlog item that will last more than one Sprint? No. A Sprint Planning event can only select Product Backlog items that can be "done" by the Scrum Team within one Sprint. You can't just plan to start work in one Sprint and finish it in the next. Of course, that happens sometimes. But that's not how you plan. Otherwise, there's no point in using Scrum. You focus on the Sprint Goal and do everything in your power to achieve it by the end of the Sprint. The Scrum Team is responsible for producing a valuable, useful Increment in each Sprint – THAT is the point and power of Scrum.
In the third part, the Scrum Team answers the question, "How will the selected work be done?" For each selected Product Backlog item, developers plan the work necessary to produce an increment that meets the Definition of Done. This is often done by breaking Product Backlog items into smaller work items of one day or less. How this is done is entirely up to the developers. No one else tells them how to turn Product Backlog items into value increments. This is another example of how self-management and empowerment work.
Now let’s summarize the topic of the Sprint Planning event.
Check out the things you should know BEFORE you plan.
– The most important Product Backlog elements (PO).
– How the most important product backlog items are assigned to the product goal (PO).
– Participants are known, invited and prepared:
i) The Scrum Team is mandatory.
ii) Do we need other people to give us advice?
iii) The participants are prepared for the discussion by the Product Owner.
– To add confidence to your sprint forecasts, know your team’s past performance, future capacity, and definition of “Done.”
Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.
