Sprint board kanban view grouped by status with story point badges

$14Project Management

Sprint Planning Board

Story points, sprint relations, and a burndown-ready backlog for small Scrum teams.

$19 Save $5

One-time payment · Instant Notion link · Yours to keep and edit forever

Secure checkout by Stripe · Full refund within 14 days

Last updated: June 10, 2026
Format: Notion page you duplicate

What's inside

Backlog database with priority, story points, and epic tags
Sprints database linked to backlog items via relation
Kanban view grouped by status: To Do, In Progress, Review, Done
Sprint timeline view for planning overlapping sprints
Committed vs. completed story points rollup per sprint
Every sprint's own page ready for retro notes — no separate tool needed
Story point estimation guide (Fibonacci scale) baked into the page

Why it holds up

Rollups calculate committed and completed points automatically
One backlog item can belong to exactly one sprint at a time via relation
Kanban, table, and timeline views of the same underlying data
Retro notes live on the sprint's own page, so they never get separated from it

Built for the team that outgrew a plain kanban board

A plain kanban board tells you what's in progress. It doesn't tell you whether a team is over-committing sprint after sprint, or whether last sprint's "almost done" items are quietly rolling over every single time. The Sprint Planning Board adds the layer a lot of small teams skip: sprints as their own linked entity, with committed and completed story points rolling up automatically so the pattern is visible instead of felt.

How the linking works

Every backlog item can be tagged with a sprint via a relation property. That single relation powers three different views — the kanban board scoped to the current sprint, a timeline showing sprint boundaries, and a rollup on the Sprints database that sums story points automatically as items move to Done. Nothing is calculated by hand, and nothing has to be kept in sync manually between views.

Getting your first sprint running

Duplicate the template, rename the two sample sprints to match your actual cadence, and drop your real backlog items in with rough story point estimates — perfect estimates aren't the goal on day one. Run one sprint, hold the retro and write it directly on that sprint's page, and adjust point estimates the following sprint based on what actually got done. The system gets more useful the second time you use it, once your team has a real committed-vs-completed baseline to compare against.

Questions people ask before buying

Does this replace Jira or Linear?

For a small team running lightweight Scrum, it can. If you need custom workflows, integrations with your codebase, or reporting across many teams, a dedicated tool like Jira or Linear is still the better fit — this template is built for teams of roughly 2-8 people who want sprint structure without another subscription.

How do I start a new sprint?

Duplicate a row in the Sprints database, set its start and end date, then filter the backlog view by 'no sprint assigned' and drag items in. The kanban view updates to show only the active sprint's items once you filter by it.

Can I track story points differently, like t-shirt sizes?

Yes — the story points property is a number field, but you can swap it for a select property with S/M/L/XL options in a few minutes. The rollup formulas will need matching adjustments, covered in a note on the page.

Is there a burndown chart?

Not a live chart — Notion doesn't render burndown charts natively. The committed-vs-completed rollup gives you the same signal in table form, updated live, without needing an external charting tool.