Agile Sprint Board Template with 6-Week Roadmap (Free)

Plan a sprint and the next six weeks on one AFFiNE page, with a filled two-week example, capacity math, blank and filled PDFs, and a backlog CSV.

Agile Project Planning page with a Sprint Dashboard and a Strategic Roadmap timeline grid showing team rows and Weeks 1 to 5

An agile sprint planning template is a one-page plan for the sprint goal, the sprint dates, and the backlog items a team commits to, set against a longer roadmap. This AFFiNE template combines a Sprint Dashboard, a six-week roadmap timeline, and a story point backlog. Below you also get a filled two-week example, PDFs, and a CSV.

What's included in this template

  • Sprint Dashboard. Fields for Current Goal, Duration, Focus, and Key Deliverable, with placeholder examples such as "Deliver the MVP for the user authentication module."
  • Strategic Roadmap (Timeline). A whiteboard grid with a Project name header, rows for the Product, Design, Development, and Operations teams, and columns for Week 1 to Week 6. It starts with three sample cards, such as "Product Team Task 1."
  • Product Backlog & Execution. A Task database with Task Name, Assignee, Status (Backlog, To Do, In Progress, Done), Column (P0, P1, P2 priority labels), Sprint (Backlog, Sprint 24, Sprint 25), Due Date, Story Points, and Tags (Frontend, Backend, Design, DevOps). It ships with four placeholder rows and a Table view.
  • Visual Workspace. An embedded whiteboard area with eight numbered boards and sticky notes for flows, architecture diagrams, or mind maps.
  • Retrospective (Sprint Review). Headings for What went well?, What can be improved?, and Action Items.

The priority field is named "Column" in the template. Rename it to Priority if that is clearer for your team.

Who it's for

  • Scrum teams planning one sprint at a time while keeping the next few weeks visible.
  • Product managers who want one page to share the sprint goal and the near-term roadmap with stakeholders.
  • Small startups and agencies that want agile structure without a dedicated project tool.
  • Student software teams running short sprints for a course project.

How to use this agile sprint planning template in AFFiNE

  1. Duplicate the template. Click Use this template to copy the page into your AFFiNE workspace.
  2. Set the sprint goal. Fill in Current Goal, Duration, Focus, and Key Deliverable before sprint planning ends.
  3. Map the roadmap. Rename the project and team rows, then place epics and milestones across Week 1 to Week 6.
  4. Size and select backlog items. Give each task a priority in the Column field and a Story Points estimate, then set Sprint to the current sprint for the tasks that fit your capacity.
  5. Update status after each Daily Scrum. Move tasks from To Do to In Progress to Done so everyone can see progress toward the goal.
  6. Close the sprint. Review the key deliverable, fill in the Retrospective section, and copy the dashboard for the next sprint.

Filled example: a 2-week MVP sprint

Example data: Brightpath, Maya, Alex, Ravi, Noor, Lee, Jordan, and every number below are fictional. The example shows how the template's fields fit together. It is not part of the AFFiNE template, and it is not a benchmark for your team.

  • Sprint: Sprint 25
  • Current Goal: New users can create an account, sign in, and reset a forgotten password on the web app.
  • Duration: Mon Nov 2 to Fri Nov 13, 2026 (10 working days)
  • Focus: Stability and security
  • Key Deliverable: Sign-up and login API plus the login and sign-up form
Illustrative render of the Sprint Dashboard filled with example data: the Sprint 25 goal, dates, focus, deliverable, and a capacity table totaling 42 developer-days with a 26-point forecast.
Illustrative render with example data, not a screenshot of the AFFiNE app.

Capacity

Maya is the Product Owner, so her time is not counted in developer capacity.

DeveloperRoleAvailable daysNote
AlexBackend10Full sprint
RaviBackend10Full sprint
NoorFrontend82 days of planned leave
LeeDesign5Half-time on this team
JordanDevOps and QA91 day on the support rota
Total42

The team completed 30, 26, and 28 points in its last three sprints, an average of 28 points. Those sprints averaged 45 developer-days. The forecast for this sprint is 28 x (42 / 45) = 26.1, rounded down to 26 points.

Story points and velocity are common team practices; the Scrum Guide does not define them. It does say that "the more the Developers know about their past performance, their upcoming capacity, and their Definition of Done, the more confident they will be in their Sprint forecasts."

Sprint backlog

Task NameAssigneeStatusColumnSprintDue DateStory PointsTags
Design login, sign-up, and error statesLeeTo DoP0Sprint 252026-11-043Design
Sign-up API with email and passwordAlexTo DoP0Sprint 252026-11-065Backend
Login API with session tokensRaviTo DoP0Sprint 252026-11-065Backend
Login and sign-up formNoorTo DoP0Sprint 252026-11-103Frontend
Password reset by emailAlexTo DoP1Sprint 252026-11-125Backend
Limit repeated failed login attemptsRaviTo DoP1Sprint 252026-11-123Backend
Run auth tests in CI on every mergeJordanTo DoP1Sprint 252026-11-052DevOps
User profile pageBacklogP2Backlog5Frontend
Sign in with Google (OAuth 2.0)BacklogP2Backlog8Backend

The seven Sprint 25 tasks add up to 3 + 5 + 5 + 3 + 5 + 3 + 2 = 26 points, equal to the forecast. The two P2 tasks (13 points) stay in the backlog. Committing exactly to the forecast leaves no buffer, so a team that often carries work over should commit below it.

Illustrative render of the Task database with nine example rows: seven Sprint 25 tasks totaling 26 story points and two P2 backlog tasks totaling 13 points.
Illustrative render of the template's Task database columns, filled with example data.

Roadmap

Sprint 25 covers Weeks 1 and 2 of the timeline. The later bars show what the team expects to work on next, such as profile pages, Google sign-in, and a private beta milestone in Week 6. They are forecasts, not commitments.

Illustrative render of the Strategic Roadmap timeline with example data: Product, Design, Development, and Operations rows across Week 1 to Week 6, with the authentication MVP in Weeks 1 and 2.
Illustrative render of the six-week roadmap grid, filled with example data.

Variants: 1-week, 2-week, Kanban, and multi-team

VariantHow to adapt this templateGood fit when
1-week sprintSet Duration to five working days and treat each week column as one sprint. Select fewer tasks and keep planning short.Priorities change often, or the team is new to sprints and wants fast feedback.
2-week sprintUse the filled example as is: one sprint spans two week columns.Work items take several days and the team wants room to finish a meaningful increment.
KanbanIgnore the Sprint field and Duration. Use Status as your workflow states and write a work-in-progress limit next to In Progress. The template does not enforce the limit for you.Work arrives continuously, such as support or maintenance, and fixed sprints add little.
Multi-teamKeep one shared backlog and one roadmap. Use the team rows in the timeline, and add a Team field to the database if Tags are not enough.Several teams work on the same product and need to see each other's milestones.

The Scrum Guide says that sprints are "fixed length events of one month or less," so choose one length and keep it. For several teams on one product, it says they "should share the same Product Goal, Product Backlog, and Product Owner." For Kanban, the Kanban Guide asks teams to define "how WIP will be controlled from started to finished." For a board built for continuous flow, see the Kanban board template.

Sprint plan vs roadmap

Sprint planRoadmap
Time spanOne sprint, one month or lessSeveral weeks or months
Question it answersWhat will we deliver this sprint, and why?What are we working toward, and roughly when?
Level of detailIndividual tasks, owners, story points, due datesEpics and milestones
How often it changesUpdated daily during the sprintReviewed at sprint boundaries or when priorities shift
Where it lives in this templateSprint Dashboard plus the Task database rows set to the current sprintStrategic Roadmap (Timeline) grid

Keep stories in the database and epics on the timeline, so the roadmap stays readable. If you need a quarter-level plan with themes and releases, use the product roadmap template instead.

Limitations and when to use another template

  • The template does not calculate capacity, velocity, or burndown. Story Points is a number field, and you do the capacity math yourself.
  • The timeline is a whiteboard grid. Dates on the cards do not update from the Task database.
  • The backlog note suggests Kanban and Timeline views, but the template ships with a Table view only, so any other view is yours to set up.
  • To run the planning meeting itself, read the sprint planning guide or use the sprint meeting agenda template.

Downloads

  • Filled sprint plan PDF: two A4 pages with the Sprint 25 example above. They cover the dashboard, a capacity block that the AFFiNE template does not have, the backlog, the roadmap, and an empty retrospective.
  • Blank sprint plan PDF: the same two A4 pages with empty fields and ten backlog rows.
  • Backlog CSV: the nine example tasks, with the same column names as the template's Task database. Multiple tags are separated by semicolons.

The PDFs are printable worksheets, not fillable forms. They are separate from the editable AFFiNE template: Use this template and Preview open the original page, which starts with placeholder text rather than the example data. The CSV opens in a spreadsheet app; importing it into AFFiNE has not been tested.

Frequently asked questions

What should a sprint planning template include?

It should include a sprint goal, the sprint dates, the backlog items the team commits to, estimates such as story points, an owner and status for each item, and a note on capacity. This template adds a six-week roadmap timeline and a retrospective section.

How long should a sprint be?

The Scrum Guide describes sprints as fixed-length events of one month or less. Many teams choose one or two weeks. Pick a length that lets you finish a useful increment and keep it consistent so your velocity numbers stay comparable.

How do I calculate sprint capacity?

Count the days each developer is available in the sprint, then compare that with past sprints. In the example, 42 developer-days against a 45-day average and an average velocity of 28 points gives a forecast of 26 points.

Can I use this template for Kanban instead of Scrum?

Yes. Ignore the sprint dates and the Sprint field, use the Status values as a continuous flow, and set a work-in-progress limit for In Progress. For a dedicated board, see the Kanban board template.

Is the downloadable PDF the same as the AFFiNE template?

No. The PDFs follow the template's dashboard, backlog, roadmap, and retrospective sections, add a capacity block, and leave out the Visual Workspace. They are static printouts. Use this template opens the editable AFFiNE page, which has placeholder text, a whiteboard roadmap, and a Task database.

Sources

  • The 2020 Scrum Guide by Ken Schwaber and Jeff Sutherland, for sprint length, the Sprint Goal, Sprint Planning, and multiple teams on one product.
  • The Kanban Guide (May 2025), for the Definition of Workflow and work-in-progress control.

Get more things done, your creativity isn't monotone