During Sprint Planning, the PO ensures that attendees are prepared to discuss the most important PBIs and how they map to the Product Goal.
During Sprint Planning we answer three important questions: a) Why is this Sprint Valuable? b) What can be done this Sprint? c) How will the chosen work get done?
The entire Scrum Team attends and collaborates on creating the Sprint Goal.
The Developers decide how many PBIs to select for the Sprint Backlog.
The developers decide on the practices to use to turn PBIs into a usable increment.
The more the Developers know about their past performance, upcoming capacity, and the DoD, the more accurate forecasts they will be able to do.
The Sprint Backlog is created during Sprint Planning and it is a combination of 3 things. i) The Sprint Goal ii) the selected PBIs, and iii) a Plan to deliver them.
The Scrum Team may invite other people to attend Sprint Planning to provide advice.
Sprint Planning is 8 hours for a 1-month Sprint and is usually shorter for shorter Sprints.
Leave a Reply
Want to join the discussion?Feel free to contribute!