Sprint Planning Document
Docs + Word3 pages
Free
- Type
- Document
- Price
- Free
- Pages
- 6 · US Letter
- Style
- Bold
- Difficulty
- Beginner
- Updated
- November 6, 2026
Every page (6)
Overview
Sprint commitments often overfill the board and leave the team guessing what to start next. Kanban replaces the commitment with limits on work in progress and a simple rule for pulling the next item. This template writes those limits, the pull and swap rules, the blocked items, the service classes and a glossary into one page the whole team can read.
The sample is for Foxhollow Software, a team of seven building a web product, with limits of four in review and one in progress per person, two blocked items and three service classes. Every name, limit and date is fictional. Replace the limits and owners with your own, and agree them with the team before you change the board.
Useful for
- A scrum master moving a team from sprint commitments to a Kanban board with limits
- A product owner deciding which ready item to pull first when the board is full
- An engineering manager reviewing blocked items and carry-over at the retrospective
What's included
- WIP limits: the limits to set, with owners, dates and the stop-the-line rule
- Items pulled: a checklist of the pull rules, with a monthly plan of the changes
- Blocked items: decisions taken, and the actions that clear each block
- Service classes: three cards on expedite, fixed date and standard work
- Notes and glossary: thirteen terms, with quotes from two team members
- Make it yours: numbered steps for setting limits, ready rules and the review
How to use it
- 1
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
- 2
Set each column's limit from the current average throughput, then review it after two weeks.
- 3
Write the ready rules and the service classes in plain words, and post them on the team board.
- 4
Replace the blocked items and owners with your own, with a clear-by date for each.
- 5
Delete the guide page, then share the notes with the team and review them at the next retrospective.
What you need
Requirements
- A Google account with access to Google Drive
Works with
- Google Docs
- Microsoft Word (download the .docx)
Questions
Are the company, people and figures fictional?
Yes. Foxhollow Software, its team members, the limits, the blocked items and every date in these notes are fictional. Replace them with your own team's board, limits and owners before you use them.
Should a Kanban team still run sprints?
It can, but it does not have to. Many teams keep a regular planning rhythm while pulling work continuously. What matters is that limits on work in progress are set and reviewed.
How often should the limits change?
Review them at each retrospective, and change one rule at a time, so you can tell which change helped. A limit that never changes is probably not being used.
- #kanban
- #wip-limits
- #replenishment
- #pull-system
- #sprint-planning
- #agile-team
- #google-docs
Related templates
More Google Docs templatesMore developer workflows templates
Agency Sprint Plan
Docs + Word7 pages
Free
Admin Training Deck
Slides + PowerPoint11 slides
Free
