Sprint planning meeting

The sprint planning is a one-day timeboxed meeting divided into two 4-hour sessions, which is also timeboxed.

  1. During the first session the Product Owner presents the highest priorities of the Product Backlog to the team. The team and the Product Owner collaborate to help the team determine what functionality can be delivered in the upcoming Sprint. The team commits to this Product Backlog at the end of the session - Selected Product Backlog.
  2. During the second session of the meeting, the team plans how it will meet this commitment by detailing its work as a plan in the Sprint Backlog.


Role Responsibilities
Scrum Master Facilitate Sprint planning meeting
Product Owner

Present product backlog
Define Sprint Goal together with the team

Team Select product backlog for the Sprint
Define Team Goal and sprint goal together with the Product Owner
Construct Sprint Backlog

Attend the Sprint planning meeting - assist with input to requirements

Sprint planning 1

Duration 4 hours
Participants Product Owner, Scrum Master, All team members, Stakeholders


Pre-requisites Preparations Expected results
  • Product backlog is prioritised
  • Backlog items are estimated
  • Planned absence of team members are known
  • The room is suitable for discussions
  • The results from Sprint review and retrospecives are available
  • Appointment for Sprint Planning 1
  • Appointment for Sprint Planning 2
  • First day of Sprint is defined
  • Last day of Sprint is defined
  • Appointment for Daily scrum meeting
  • Appointment for Sprint review meeting
  • Appointment for Retrospective


  1. Make visible to everyone
  2. The Product Owner informs team about the product vision
  3. The Product Owner and the team defines the Sprint goal
  4. The team selects as much Product Backlog as it believes it can develop during the next Sprint
  5. Lower priority items may be included if appropriate and Product Owner agrees
  6. The Product Owner and team mutually agree on the Sprint goal and the Selected Product Backlog


If backlog items are missing the Product Owner can add Backlog items

If the backlog is completely without estimates

  • Select the item to be the smallest story and assign it score 2
  • Assign Story points to the other backlog items relative to the smallest one

If there are some backlog items which are not estimated yet, estimate backlog items in relation to the other ones.

If Product Backlog is not properly prioritized, the Product Owner re-prioritizes.

Sprint planning 2

Duration 4 hours
Participants Scrum Master, All team members, Product Owner (reachable for questions)


Pre-requisites Preparations (optional) Expected results
  • Selected Product Backlog
  • A huge pinboard or flip charts
  • Post its for tasks
  • Marker pens


  • Daily-scrum to enter tasks directly


  1. Team members identifies tasks for each backlog item
    • Design
    • Coding, testing and reviews
    • Meetings
    • Learning new techniques
    • Documentation
  2. Estimate tasks
    • If a task effort is more than one day, try to split it into smaller tasks
  3. Consolidate
    • If the team believes the backlog is too large remove backlog items together with the Product Owner
    • If the team believes the backlog is too small, select the most important backlog items from the Product Backlog together with the Product Owner, and plan these items.
  4. The team commits to the Selected Product Backlog, the Sprint Backlog and the Sprint goal

The Sprint goal and the sprint backlog should be visible to everybody in the organization.
The tasks in the Sprint Backlog should be accessible to all Team members.