Plan a two-week sprint: set the goal, pull and estimate stories within capacity, then track to done.
A sprint planning template is a ready-made board for agile teams that sets a sprint goal, pulls estimated stories from the backlog into the sprint within the team's capacity, and tracks them to done.
Sign in with your Edesy account, then click Use template in the preview to create the board, with its sample cards, in your workspace.
Ideal for
Columns
Backlog → Sprint goal → To do → In progress → Review → Done
Sample cards
8
Custom fields
Story points, Sprint
Request form
Creates cards in Backlog
Updated
2026-11-19
The 6 columns of this board with its 8 sample cards, labels and fields, as they open in Edesy Boards. Copy the template to move cards and edit it.
Labels
Story, Bug, Spike, Tech debt, Blocked, Sprint goal
Custom fields
Story points (Single select, on card), Sprint (Text, on card)
Request form: Submit a story or bug · Sprint Planning
Tell us what you need; it lands on the “Backlog” column of this board. Asks for Title, Description, Priority, Story points, Attachments; each submission becomes a card in Backlog.
Card templates
User story, Bug
The product backlog holds every story, bug and spike that might be worked on. Items from the request form land here, so the product owner decides what enters a sprint.
A dedicated column keeps the sprint goal and the stories that directly serve it visible all sprint. When trade-offs come up mid-sprint, the team checks them against this column.
To do is the sprint backlog the team committed to. In progress shows what each person is working on for the stand-up, and Review holds work waiting for code review or the product owner's check, a common place for stories to stall.
Moving a card to Done completes it, so the insights view shows throughput, and the sprint review covers exactly the cards in this column.
Story points is a single-select so estimates stay on the agreed scale; adding up the points in To do tells you whether the sprint fits the team's capacity. The Sprint field records which sprint a card belonged to, which helps when unfinished work carries over.
Type labels show how the sprint is split between new work, fixes, research and clean-up. Blocked makes impediments visible on the board, and swimlanes by label can group blocked cards at the top.
The form asks for a title, description, priority, story points and attachments, so stakeholders can add requests without editing the board. The User story and Bug templates keep acceptance criteria and checklists consistent.
This sprint planning board is set up for a two-week sprint. It has six columns: Backlog, Sprint goal, To do, In progress, Review and Done, which is the done stage. Two custom fields sit on every card: Story points, a single-select with Fibonacci-style values such as 1, 2, 3, 5, 8 and 13 in the samples, and Sprint, a text field holding the sprint name such as S24. Six labels sort the work: Story, Bug, Spike, Tech debt, Blocked and Sprint goal. The sample cards follow a SaaS team planning sprint 24 around self-serve plan upgrades: the sprint goal card, a grooming card with write acceptance criteria, estimate, implement, write tests and demo, an upgrade flow UI story, proration logic, a capacity note that a developer is on leave for three days, a flaky checkout test, a spike comparing Stripe and Razorpay subscriptions with research, write findings and decide, and sprint demo preparation in Done. A Submit a story or bug form lets stakeholders add items to the Backlog with a priority and story points, and two card templates, User story and Bug, keep new items consistent.
It is for scrum and agile software teams of three to ten people, product managers and engineering managers who run sprint planning, and agencies delivering client work in sprints. It suits teams that find heavy agile tools too much and want planning, the daily stand-up and the sprint review on one board. Teams new to scrum can use it to learn the flow from backlog to done.
Click Use this template, sign in with your Edesy account, then click Use template in the preview to create the board with its sample sprint.
Before planning, groom the Backlog: write acceptance criteria and set Story points on each candidate story; delete the sample cards.
In the planning meeting, write the sprint goal as a card in Sprint goal, then move stories into To do until their points reach the team's capacity, noting leave and holidays as capacity cards.
Set the Sprint field on each committed card, assign owners and add the Blocked label to anything stuck, then use the board in daily stand-ups.
At the end of the sprint, review what reached Done, move unfinished stories back to the Backlog and archive completed cards before the next planning.
Story points is a select field shown on each card, so you can read it at a glance, but the board does not total it per column. Use the list view to see points side by side, or export the board to CSV to sum them.
At sprint end, move unfinished cards back to Backlog or To do and update the Sprint field to the next sprint name. Their comments and checklists stay with them.
Yes. Use swimlanes by assignee so each person's cards sit in one row, and walk the In progress and Review columns. The Blocked label shows what needs help.
Yes. Share the Submit a story or bug form link. Each submission lands in Backlog with its description, priority and suggested story points for the team to review.
Yes. Give cards start and due dates and switch to the timeline view to see the sprint as bars, or the calendar view for due dates.
Yes. Create cards for planning, review and the retrospective and set them to recur, for example weekly, so a fresh card with a new due date appears on schedule.
Yes, through the board request form. Share its public link; each submission becomes a card in the chosen column, with the answers in the card fields. Viewers of a shared read-only board link can see the board without an account.
Yes. Board automations run when a card is created, moved, assigned, labelled, completed, due soon or overdue, when a form is submitted or on a schedule, and can move, assign, label or archive the card, add a checklist or comment, create another card, call a webhook or post to Slack.
A general agile board from product backlog to done, with story points, code review and QA stages.
6 columns · 6 sample cardsAgile Project Plan TemplatePlan a project the agile way: a release goal broken into sprints, stories and recurring ceremonies.
6 columns · 7 sample cardsAgile Schedule TemplateSchedule work across upcoming sprints so priorities and release dates stay realistic.
5 columns · 6 sample cardsAgile Scrum TemplateA ready-made scrum board for a product team: backlog, sprint backlog, development, code review and QA.
6 columns · 7 sample cardsAgile Sprint Weekly Status Report TemplateReport sprint progress each week: what is to do, in progress and done, plus blockers and burn-down.
4 columns · 6 sample cardsBacklog Grooming TemplateGroom the product backlog: clarify user stories, add acceptance criteria and estimate before planning.
5 columns · 7 sample cards