How to Track Scrum Metrics in Notion: Velocity & Burndown

You’ve set up your Scrum workflow in Notion, but tracking metrics like velocity and burndown feels clunky without native chart widgets. Notion doesn’t offer built-in Scrum analytics, but you can calculate and visualize both metrics using databases, rollups, and formulas.

This guide walks you through building a velocity tracker and burndown chart system inside Notion. You’ll learn which properties to add, how to structure your databases, and where to find the numbers you need for sprint planning.

Why Track Scrum Metrics in Notion?

Velocity and burndown charts answer two critical questions: how much work your team completes each sprint, and whether you’re on track to finish the current sprint. Most dedicated Scrum tools auto-generate these charts, but Notion requires you to build the logic yourself.

The upside? You control every formula and can adapt the system to hybrid workflows—like combining Scrum with OKRs or workload tracking. The downside is you’ll need to update story points manually and refresh rollups to see changes.

If you run AI projects alongside your sprints, the AI Project Command Center template includes a sprint database pre-configured with velocity rollups and a prompt library for generating user stories.

What You Need Before You Start

Two linked databases: one for sprints, one for tasks (user stories, bugs, etc.). If you haven’t built these yet, follow the setup in our Notion agile workspace guide.

Story points assigned to every task. Use a number property in your tasks database. Fibonacci scale (1, 2, 3, 5, 8, 13) works well, but any consistent point system will do.

A status property that includes at least “To Do,” “In Progress,” and “Done.” You’ll filter rollups by status to separate planned from completed work.

Step 1: Set Up Your Sprints Database

Create a new database called “Sprints.” Add these properties:

• Sprint Name (title): e.g., “Sprint 12” or “Q1 Sprint 3”
• Start Date (date)
• End Date (date)
• Sprint Goal (text, optional): a one-sentence objective
• Tasks (relation to your tasks database)

Add a rollup property called “Total Story Points.” Point it to the Tasks relation, then select your story points property. Choose “Sum” as the calculation. This shows how many points you committed to at the start of the sprint.

Add a second rollup called “Completed Story Points.” Use the same relation and story points property, but add a filter: only include tasks where Status = Done. This is your velocity for that sprint.

Step 2: Add Story Points and Status to Your Tasks Database

If you don’t already have these, add a “Story Points” number property and a “Status” select property to your tasks database. Every task that counts toward a sprint needs a story point value—even if it’s just 1 for small bug fixes.

Link tasks to sprints using the relation property. When you plan a sprint, select all the tasks you’re committing to and assign them to the sprint record in your Sprints database. Notion will auto-populate the rollups once tasks are linked.

You can also add a formula in your tasks database to calculate points remaining. Use this formula:

if(prop("Status") == "Done", 0, prop("Story Points"))

This returns 0 for completed tasks and the original story points for everything else. You’ll use this for burndown tracking.

Step 3: Build a Velocity Tracker

Create a new view in your Sprints database called “Velocity Tracker.” Show it as a table and include Sprint Name, Start Date, End Date, Total Story Points, and Completed Story Points.

Add a formula property called “Velocity.” Use this formula:

prop("Completed Story Points")

This simply mirrors your completed rollup, but you can extend it to calculate percentage complete or average velocity over the last three sprints if you prefer.

Sort by Start Date descending so your most recent sprint appears at the top. After a few sprints, you’ll see a history of how many points your team delivers per sprint. Use the average to guide future sprint planning.

Notion doesn’t auto-generate line charts, so if you want a visual graph, export the table to CSV and paste it into Google Sheets or Excel. Create a simple line chart with sprint names on the X-axis and velocity on the Y-axis.

Step 4: Calculate Burndown for the Current Sprint

Burndown charts show how many story points remain each day of the sprint. Notion doesn’t support daily snapshots natively, so you’ll either track manually or use a workaround.

Manual method: At the end of each day, add a new row to a “Daily Burndown” database with the date and a rollup of remaining points. Relate this database to your current sprint, then add a rollup that sums “Points Remaining” (the formula you built in Step 2) across all linked tasks.

Automated workaround: Use a third-party tool like Zapier or Make to take a daily snapshot of your remaining points rollup and log it to a new database row. This requires a paid Zapier plan and some setup time, but it removes the manual logging step.

Most small teams find the manual approach good enough—it takes 30 seconds during your daily standup to log the number. If you’re running a remote team, assign the task to your Scrum Master or rotating team member.

Step 5: Visualize Burndown with a Table or Chart

Create a “Daily Burndown” database if you haven’t already. Add these properties:

• Date (date)
• Sprint (relation to your Sprints database)
• Remaining Points (rollup from Sprint → Tasks → Points Remaining formula, sum)

Each day, create a new entry with today’s date, link it to the active sprint, and the rollup will auto-calculate remaining points. After a few days, you’ll see the trend.

To visualize it, export the Daily Burndown table to Google Sheets and create a line chart with Date on the X-axis and Remaining Points on the Y-axis. Add a reference line showing your ideal burndown (total points divided evenly across sprint days).

If you prefer to keep everything in Notion, use a table view sorted by date and scan it visually during sprint reviews. It’s less polished than a chart, but it gives you the same insight: are you burning down faster or slower than planned?

Step 6: Use Velocity to Plan Future Sprints

Calculate your average velocity by adding up Completed Story Points from your last three to five sprints and dividing by the number of sprints. This is your planning baseline.

When planning a new sprint, filter your backlog by story points and select tasks until you hit your average velocity. Resist the urge to overcommit—velocity is an average, not a target to beat every sprint.

If your velocity is trending down, look for patterns: are tasks under-estimated? Is the team being pulled into unplanned work? Use your sprint retro notes to track these insights over time.

You can also break down velocity by task type (feature, bug, tech debt) using a second rollup filtered by a “Type” select property. This helps you see if certain categories slow your team down.

How to Track Metrics Across Multiple Teams

If you manage multiple Scrum teams, add a “Team” select property to both your Sprints and Tasks databases. Filter your velocity tracker by team to see per-team performance.

Create a master rollup in a Teams database that sums velocity across all sprints for each team. This gives you a high-level view without switching between databases.

For cross-team dependencies, use Notion relations and rollups to link tasks from different backlogs. You can also set up a shared “Blocked” status and track how often dependencies slow down sprints.

Common Pitfalls and How to Avoid Them

Story points change mid-sprint. If you re-estimate tasks after planning, your Total Story Points rollup will shift and your velocity calculation will be off. Lock story points once a sprint starts, or add a separate “Original Estimate” property that doesn’t change.

Rollups don’t refresh instantly. Notion rollups update when you reload the page or switch views. If your burndown number looks wrong, refresh your browser before logging it.

Tasks span multiple sprints. If a task isn’t finished by the end of a sprint, either move it to the next sprint (and remove it from the old sprint relation) or split it into smaller tasks. Don’t let tasks live in two sprints at once—it double-counts story points.

When to Use Notion vs. a Dedicated Scrum Tool

Notion works well for small teams (3–8 people) who want to keep their backlog, docs, and metrics in one workspace. It’s especially useful if you’re already using Notion for client work, content planning, or tracking AI experiments.

If you need real-time burndown charts, sprint reports, or integration with version control, tools like Jira or Linear are better fits. They auto-generate metrics and handle edge cases (like partial story points or task splits) without manual formulas.

For hybrid setups—like tracking sprints in Notion but using GitHub for issue tracking—you can embed GitHub project boards in Notion or use Zapier to sync task status. Check the AI Tools category for automation ideas that connect Notion to other platforms.

How to Export and Share Metrics with Stakeholders

Create a “Sprint Summary” template in Notion with embedded views of your velocity tracker and burndown table. At the end of each sprint, duplicate the template, link it to the finished sprint, and share the page with stakeholders.

For visual reports, export your velocity and burndown tables to Google Sheets, generate charts, then embed the Sheets file back into a Notion page. This gives you live-updating graphs without leaving Notion.

If you run sprint reviews with non-technical stakeholders, add a simple text summary at the top of your sprint page: “We completed 23 of 28 story points. Three tasks moved to the next sprint due to a late design change.” Context beats charts for most audiences.

Frequently asked questions

Can Notion automatically generate burndown charts?

No, Notion doesn't have native burndown chart widgets. You need to manually log remaining story points each day in a database and export the data to Google Sheets or Excel to create a line chart. Some teams use Zapier to automate daily snapshots, but that requires a paid integration plan.

How do I calculate velocity in Notion?

Add a rollup property to your Sprints database that sums the story points of all tasks where Status = Done. This rollup shows your velocity (completed story points) for each sprint. Average the last 3-5 sprints to get your baseline for future planning.

What if my story points change after the sprint starts?

Lock story points once sprint planning is done, or add a separate 'Original Estimate' property that doesn't change. If tasks are re-estimated mid-sprint, your Total Story Points rollup will shift and your velocity calculation will be inaccurate.

Can I track Scrum metrics for multiple teams in one Notion workspace?

Yes. Add a 'Team' select property to your Sprints and Tasks databases, then filter your velocity tracker by team. You can also create a master Teams database with rollups that sum velocity across all sprints for each team.

Do I need a paid Notion plan to track Scrum metrics?

No. Rollups, relations, and formulas work on Notion's free plan. You only need a paid plan if you want advanced permissions, version history, or larger file uploads. All the database features for velocity and burndown tracking are available for free.

How often should I update my burndown chart in Notion?

Daily is standard. Log remaining story points at the end of each day (or during your daily standup) so you can spot trends early. If daily feels like overkill for your team, tracking every 2-3 days still gives you useful sprint progress visibility.