Free product template
Sprint plan
People, days off and focus factor, a sprint goal, the stories that carry it, a burndown preview and a board.
It opens with this template loaded and runs in your browser. You don't need an account to use it; a free account saves your work and exports it.
The job it does
At sprint planning: fit the work to the team you actually have, and see what will carry over before the sprint starts. It comes with its own checks, so after you change it you can see at a glance that it still does the job.
What's inside
This is the template exactly as the Product & BA Lab opens it, read-only. Open it to run it, change it and export it.
- 1 document
- Exports as Markdown and CSV
A sprint planned against real capacity: people, days off and focus factor, a goal, the stories that carry it, and what waits in the backlog. Put your own team and backlog in and keep the sprint inside the line.
- The sprint fits the team’s capacity
- The sprint has a goal and stories to meet it
- The sprint uses at least 70% of capacity
Goal: Partners can reorder last week’s basket in two taps, offline included
Capacity: 4 people × 10 days (minus 1 days off) = 39 person-days × focus 0.65 × 1 points a day = 25.4 points. Committed: 21 points in 4 stories: fits. Burndown preview: at this capacity the sprint burns down by the last day.
In the sprint
| Story | Points | Priority | Owner | Status |
|---|---|---|---|---|
| Reorder button on order history | 5 | P1 | Nadia | To do |
| Copy last basket to the cart | 8 | P1 | Developer 2 | To do |
| Queue a reorder with no signal | 5 | P1 | Nadia | To do |
| Reorder analytics events | 3 | P2 | Tester | To do |
Likely carry-over
Nothing: the sprint fits.
Backlog
- Partner app dark mode (5 points, P3)
- Weekly reorder reminder (3 points, P2)
The lesson behind it
Learn why it works, with a podcast and a quiz for each lesson.
More product templates
Process map: as-is and to-be
A swimlane map with lanes per team, decisions with labelled outcomes and a validator; the today and the proposed process side by side.
Backlog prioritisation (RICE and MoSCoW)
Reach, impact, confidence and effort for every item, a MoSCoW board, and why for every number.
Requirements traceability matrix
Requirements, user stories and test cases, linked, with every coverage gap highlighted.