Average Velocity is a useful metric for resource planning within a given team. Not only does Average Velocity give you one measure of a team’s speed, it will also provide you with a building block for the important metric Backlog Health, which we will discuss next.

This will be our first metric based on a recipe in Notion. A quick note on terms:

Ingredients are what we call a single data point tracked over time in Notion. Recipes are what we call metrics that are based on a formula and can include one or more ingredients or fixed numbers.

Average Velocity will require two steps, 1) creating an ingredient from JIRA using our JQL template to pull in your completed story points in a three-iteration window and 2) creating a recipe that divides that ingredient by 3 to get the average.

To get our first number, we will use the custom JQL feature from the JIRA integration.

The JQL you want to use is the one that will filter your tickets by whatever your “done” status is. Here is an example JQL:

project IN ('Project1') AND status in ("Resolved","Closed") AND issuetype = "Story" AND resolved >= endOfWeek ("-10w") AND resolved <= endOfWeek("-4w”)

This example filters for every ticket that is closed or resolved in Project1 and was resolved in a 6 week period starting 4 weeks ago.

We use a 6 week window so that we can take an average over 3 iterations. The window starts four weeks ago, so that we avoid overlap with current sprints.

Then set the ingredient to sum by story points and set the reporting frequency to match up with your iteration period, unless you want to have a more granular view of your Average Velocity.

Then just pick your dashboard and build it out.

With this ingredient created you can now build an Average Velocity recipe in Notion. From the dashboard select New Metric>> Create a Recipe.

Now Call the recipe something like “Average Velocity for X Team”, then set the formula to be equaled to the Total Completed Story Points ingredient from the last step divided by the fixed number 3. Like this:

Set the date range to correspond with your iteration period

Now you will have a metric that shows you your team’s Average Velocity.

Next up: Use your Average Velocity in another recipe: Backlog Health