Skip to content
The first pages of the Sprint Planning Document template

Sprint Planning Document

Document template for Google Docs and Word

Make a copy in Google Docs
Price
Free
Style
Bold
Difficulty
Beginner
Updated
November 1, 2026

Every page (3)

Overview

Sprints go wrong when the goal is a list of tickets and the commitment ignores leave, on-call load and the team's real average velocity. This template keeps planning to a few pages: the sprint goal with key dates and a calendar, a checklist of committed and stretch items with owners and due dates, risks and dependencies, and the definition of done.

The sample follows a seven-person Glenmoor Cloud team in sprint 14: 55 available days at a 0.65 focus factor gives 36 points, a 3-sprint average of 37, and a commitment of 31 points (84%) with 5 points of stretch. Replace the dates and goal, enter each person's available days and move anything above 90% of average velocity to stretch.

Useful for

  • A scrum master running sprint planning for a team of five to nine and recording what was committed
  • A product owner checking which items fit the sprint and which move to stretch
  • An engineering manager reviewing risks, dependencies and on-call load before the sprint starts

What's included

  • Sprint goal and key dates as a timeline, with a compact calendar of the sprint month
  • Capacity calculation and commitment against the 3-sprint average
  • Committed items with estimates, owners and due dates
  • Stretch items, risks and dependencies with owners and the date each must land
  • Definition of done checklist
  • Guide page for replacing the sample content

How to use it

  1. 1

    Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.

  2. 2

    Set the sprint dates and replace the goal with a single outcome sentence, not a list of tickets.

  3. 3

    Enter each person's available days, apply your focus factor and commit no more than 90% of your 3-sprint average velocity.

  4. 4

    Replace the items with your refined backlog, each with an estimate and owner, and name the owner and delivery date of each dependency.

  5. 5

    Delete the guide page at the end, then share the document with the team.

What you need

Requirements

  • A Google account with access to Google Drive

Works with

  • Google Docs
  • Microsoft Word (download the .docx)

Questions

How much should we commit in a sprint?

Aim for 80 to 90% of your 3-sprint average velocity, then add one or two stretch items. Committing to your best-ever sprint almost guarantees carry-over.

Is this only for two-week sprints?

No. The sample uses two weeks, but you can change the dates and recalculate capacity for one-week or three-week sprints. The checklist and timeline work the same way.

Are the company and figures real?

No. Glenmoor Cloud, its people, email addresses and every figure are fictional sample data. Replace them with your own team, dates and estimates before sharing.

  • #sprint-planning
  • #scrum
  • #sprint-goal
  • #team-capacity
  • #agile
  • #sprint-backlog
  • #definition-of-done

More sprint planning templates

See all 3

Also in Developer workflows

All developer workflows templates
Get this template

Preparing your template…