Scrum template

Running scrum well means keeping your backlog, sprint plans, and daily updates in sync without losing time to spreadsheets or disconnected docs. This free scrum template gives your team one connected place to manage user stories, plan sprints, track progress on a live sprint board, run standups, and turn retrospective feedback into action, with built-in AI to help estimate story points and clean up acceptance criteria along the way.

​

Try the template

​

​

What is a scrum template?

A scrum template is a structured, repeatable way of running a team's work within the broader agile framework, covering backlog, sprints, and ceremonies such as daily standups, sprint reviews, and retrospectives. It gives a scrum team a shared process for prioritizing work, planning what to build next, and tracking progress without starting from scratch every sprint. This free scrum template covers the full cycle, from a prioritized product backlog through sprint planning, a live scrum board, daily standups, and end of sprint retrospectives, all connected in one workspace.

​

​

Why use a scrum template?

A spreadsheet or a stack of sticky notes can track a single sprint, but they break down the moment stories, standups, and retrospective notes need to connect to each other. This scrum template keeps your product backlog, sprint backlog, and ceremony notes linked, so a story's status update automatically reflects on the scrum board and a sprint's capacity is checked against what the team has actually committed to, no matter which agile methodology your broader team follows or which other agile tools it already uses. It's built for scrum masters, product owners, scrum teams, and agile project management teams who want the structure of scrum without manually reconciling backlog spreadsheets, standup notes, and retrospective docs. Because it's a free template, it's easy to scale from a single small team to multiple teams running parallel sprints, and simple to customize as your workflow changes.

​

​

Benefits of a scrum template

A good scrum template keeps every part of the sprint cycle connected, so nothing falls through the cracks between planning and delivery. Here are some benefits:

• Clearer prioritization. Grouping user stories under epics makes it easy to see how much work each initiative represents. Story point rollups on each epic show total effort at a glance, so product managers can prioritize based on size, not guesswork.
• Sprint capacity that's actually enforced. Instead of hoping a sprint doesn't get overloaded, an automation flags the team when committed story points exceed the sprint's capacity, catching overcommitment during planning instead of mid sprint.
• Faster estimation. The Suggested Story Points Field Agent reviews a story's description and acceptance criteria and proposes an estimate, giving the team a starting point instead of estimating every story from a blank slate.
• A closed feedback loop. Notes from each scrum retrospective turn directly into tracked action items with owners and due dates, so improvement ideas don't get lost once the meeting ends.
• Real-time status without extra status meetings. Moving a story across the scrum board's backlog, to do, in progress, and done columns keeps sprint progress visible to the whole team without extra reporting.

​

​

How to use a scrum template

This scrum template is easy to use, with data already set up for backlog, sprints, standups, and retrospectives, so you're not building structure from scratch. After you click "Try the template," you can start adding your own stories right away. Here's how to get started in a few steps:

​

Build your product backlog and group it into epics

Add user stories to the User Stories data with a title, description, acceptance criteria, and priority. Group related stories under an epic in the Epics data, so features stay organized as a set rather than a loose list of tasks. Once stories are grouped, story point rollups on each epic show how much work that feature represents, which makes it easier to decide what to tackle next.

​

Plan a sprint

Create a sprint in the Sprints data with a sprint goal, start and end dates, and a team capacity in story points. Rather than keeping this cycle's project plan in a separate document, capture the goal, dates, and capacity directly here, then assign backlog stories to the sprint based on priority and size. With capacity set, an automation alerts the team if the stories committed to the sprint add up to more story points than the team can realistically deliver.

​

Run the sprint on the scrum board

Open the Sprint Backlog Scrum Board view to see every story assigned to the current sprint, organized into backlog, to do, in progress, and done columns. Move stories across the board as work progresses, giving the whole team visibility into sprint progress in real time.

​

Log daily standups

Use the Daily Standups data to capture what was done, what's next, and any blockers for each day of the sprint. The Daily Standups by Sprint view groups these updates by sprint, so the team can spot recurring blockers before they turn into roadblocks that slow the whole sprint down.

​

Close the sprint with a retrospective

At the end of the sprint, log what went well and what didn't in the Retrospectives data. Turn the improvement ideas that come out of that discussion into Action Items with an owner and a due date, so the retrospective leads to real changes in the next sprint instead of getting forgotten.

​

​

Tips for using a scrum template

This template is easy to use out of the box, but a few habits help your team apply core scrum principles more consistently. Here are some tips:

• Run the Suggested Story Points agent before planning. Generating a story point suggestion before your sprint planning session gives the team a consistent starting estimate instead of debating from zero, which speeds up capacity planning for the sprint.
• Clean up acceptance criteria as you write stories. Run the Cleaned Acceptance Criteria agent on stories with messy or informal notes, so every story in the backlog reads clearly no matter who wrote it, which keeps the team's scrum methodology consistent from story to story.
• Watch the capacity alert closely during sprint planning. Since the automation flags a sprint when committed story points exceed capacity, treat that alert as your cue to cut scope or split a story rather than pushing the team past what it can deliver.
• Review epic rollups before every planning session. Comparing story point totals across epics helps product managers decide which epics deserve the next sprint's capacity, instead of managing priority in a separate product roadmap document.
• Use standups to catch impediments early. Logging blockers daily in the Daily Standups data, rather than waiting for the daily standup meeting to surface problems out loud, makes it easier to catch impediments before they stall the sprint.

​

​

What's included in the scrum template

A scrum template typically includes a backlog, a sprint board, and a place to run standups and retrospectives, but this one goes further with built-in automation and AI. Every data set and view below is included out of the box, and you can customize any of it just by describing what you need to Omni, Airtable's built-in building expert. Here's what's included in this template:

• User Stories data. The backlog table holding every story's title, description, acceptance criteria, story points, status, and priority, along with links to its epic and sprint.
• Epics data. Groups related stories together and rolls up their total story points, so you can see how large each feature is before committing it to a sprint.
• Sprints data. Holds each sprint's goal, start and end dates, and team capacity in story points, and connects out to standups and retrospectives for that sprint.
• Daily Standups data. A daily log of what was done, what's next, and any blockers, organized by sprint in its own view.
• Retrospectives and Action Items data. Captures what went well and what didn't after each sprint, then turns improvement ideas into tracked action items with an owner and due date.
• Sprint Backlog Scrum Board view. This scrum board template shows every story in the current sprint organized into backlog, to do, in progress, and done columns, with burndown insight into how much work remains against the sprint goal.
• Status change notifications. An automation that lets a story's owner know when its status changes, so updates don't get missed between standups.
• Capacity alerts. An automation that flags the team when a sprint's committed story points exceed its capacity, so overcommitment gets caught during planning instead of mid sprint.
• Suggested Story Points (Field Agent). Reviews a story's description and acceptance criteria and suggests an effort estimate, speeding up backlog grooming and keeping estimates consistent across the team.
• Cleaned Acceptance Criteria (Field Agent). Rewrites messy or informal acceptance criteria into a clear, consistent format, so every story in the backlog reads the same way.
• No-code customization with Omni. Just describe what you need, and Omni builds it, whether that's a new view for a specific team, an added field for tracking risk, or an automation for a workflow this template doesn't cover yet.
• AI-powered reporting with Omni. Ask Omni questions about your data directly, like which epics have the most story points left unplanned or how many blockers came up this sprint, and get an answer without building a new view.

​

​

Other examples of scrum templates

As there are different styles of managing sprints, there are also different templates to fit each part of the process. These are free and can be used by different types of teams alongside whichever project management style they already run.

​

RACI template

Maps every project task to a responsible, accountable, consulted, and informed role, so project managers and stakeholders always know who owns what and can catch accountability gaps before they cause delays.

​

Try the template

​

Agile template

Connects backlog, sprints, standups, and retrospectives in one flexible workspace, giving agile teams a single place to plan work, track stories, and stay aligned from kickoff through release.

​

Try the template

​

Sprint planning template

Brings sprint goals, backlog grooming, and team capacity into one connected workspace, helping scrum masters and development teams commit to realistic sprints and carry retrospective learnings into the next one.

Try the template

​

Product planning template

Tracks customer needs, product ideas, and launches across the full product life cycle, giving product teams a single source of truth from early concept through market release.

Try the template

​

​

Customize your scrum template with Claude

Airtable connects to Claude through MCP, so you can update stories, check sprint progress, and review retrospectives from a conversation instead of opening the template each time. Here are some prompts to try:

• "Show me every user story in the current sprint that doesn't have story points yet."
• "Summarize this sprint's blockers from the daily standups."
• "Draft acceptance criteria for a new user story about [feature], based on similar stories already in the backlog."

​

​

Run your next sprint with Airtable

When a scrum team tracks its backlog in one document, sprint plans in another, and standup notes in a chat thread, sprint progress falls through the cracks. Airtable's scrum template brings it all into one place, with customizable views, flexible workflows, and built-in AI that estimates story points and cleans up acceptance criteria as the backlog grows. Your team spends less time reconciling tools, and more time actually running the sprint.

​

Try Airtable's scrum template today and give your next sprint a home that keeps up with it.

​

​

Frequently asked questions

​

What's the difference between a scrum board and a kanban board?

A scrum board tracks a fixed set of stories committed to a single sprint, while a kanban board tracks a continuous flow of work with no set sprint boundary. This template's Sprint Backlog Scrum Board view follows the scrum approach, showing only the stories assigned to the current sprint as they move from backlog through to done.

​

How long should a sprint be?

Most scrum teams run sprints between one and four weeks, with two weeks being the most common length. You can set your sprint's length directly in the Sprints data by choosing a start and end date that fits your team's pace.

​

What are the three questions asked in a daily scrum meeting?

A daily scrum meeting typically covers what was done since the last update, what's planned next, and whether anything is blocking progress. The Daily Standups data captures all three, so the team has a running record instead of relying on memory from one standup to the next.

​

What's the difference between a product backlog and a sprint backlog?

A product backlog holds every story the team might work on across all epics, while a sprint backlog is the subset committed to the current sprint. In this template, the User Stories data acts as the product backlog, and the stories linked to an active sprint make up that sprint's backlog on the scrum board.

​

What is a burndown chart used for?

A burndown chart shows how much work remains in a sprint compared to how much time is left, so a team can see early whether it's on track to meet the sprint goal. This template's scrum board provides that same burndown insight, tracking remaining story points against the sprint as work moves across the board.