The Scrum Team to determine what they will work on for the new sprint based on product priority and team capacity.
When does it Occur?
The Sprint Planning Part 1 event occurs on day 1 of the new sprint and before any work begins. 30-60 minutes
Who Participates?
The Product Owner and team members doing the work participates (aka the Scrum team).
What is the Outcome?
User Stories are pulled into the Sprint from the backlog based on priority and team capacity.
The team ensures all work committed/planned for the Sprint is:
- Sized/Estimated (or average lead time for defects)
- Has Acceptance Criteria
- Meets INVEST standards
- Has an outcome and/or value
Scrum Master’s role in the Sprint Planning
- Ensures Event (aka meeting) Outcome is met (see table)
- Servant Leader who Leads by example
- Facilitates Event
- Manages the logistics (example: Owns calendaring the Event)
- Fosters Agile Mindset
- Coaches people in attendance and people leaders
- Time boxes Events so that goals and event outcome is accomplished
- Teaches people who are new to the event or new to the team
Product Owner’s role in the Sprint Planning
- Is the Voice of the Customer / Product
- Listens to understand the team understands the Outcome and Value ask during the event and has a plan on how to deliver against the plan by the end
- Listens to understand how the team is breaking down the work and asks questions to determine if there is additional work, additional acceptance criteria, or if the outcome can be accomplished within the sprint
- Listens to understand that all work planned during the sprint moves towards the Sprint Goal and Product Outcome/Value
- Understands that the team can accomplish the Sprint Plan / Commitment / Forecast
- Brings with them and tells the team the priority AND rank (1-n) of work
- Answers questions about the work, acceptance criteria or outcome/value
- Answers questions related to strategy and tactical to ensure team is delivering the right solution for the outcome or value
- Guides the team on splitting the work if additional scope/requirements are found during sprint planning
- Listens to understand how the technical solution will deliver the outcome and value to make decisions
Team Member’s role during Sprint Planning
- Actively involved in Event
- Asks questions and provides information or context to ensure everyone understands the work, potential gaps in Acceptance Criteria, potential new requirements, and/or anything impeding delivering the outcome or value within the Sprint
- Communicates findings or technical changes so that all team members have the same information and in case this impacts other people’s work or future work
- Ensures they are working on the highest rank order/priority item
- Communicates time planned on any work that is not part of asks by the Product Owner, as they should be included in the Sprint Plan / Commitment / Forecast
- Ensures the tools are updated with all work planned by the end of the event
Non-team Members’ Role during the Planning Event
- Non-team members are chickens (from the pig/chicken story).
- They are not doing work.
- They might be SMEs, people leaders, or from a group (i.e. Solutions)
What tools should the Scrum Master and the Team uses prior to and during the event
- Collaboration
- Physical Sprint Board
- JIRA Sprint Board (Artifact)
- Story Maps, Journey Maps, Event Storming Maps
- Confluence (as needed)
See also: Sprint Planning Part 2 (Task Breakdown)