Is there any possibility to see the average sprint velocity in Jira?
Asked by Alexandra Walther:

If I have a look a the Jira Velocity Report I do see the completed and commited Storypoints per Sprint, but I don't see the average velocity which helps me to get an impression of the speed of my Team.  
Is there any chance to see this without buying and addon and manually calculating it?  

Thanks to all :-)


Answers:
author: Alexandra Walther
body: I was searching a bit more in the Atlassian Community and in the Backlog for Jira Cloud and found a feature request raised in 2013.  

So I can answer myselfe - the average velocity is not easily available in JIra Cloud. So I'll keep watching the feature request and hope it will be implemented one day so that I can stop calculating it manually.  

[JIRA BACKLOG ITEM - AVERAGE VELOCITY](https://jira.atlassian.com/browse/JSWCLOUD-7653)


author: Danut M _StonikByte_
body: Hi [@Alexandra Walther](/t5/user/viewprofilepage/user-id/234333),

As you can see, this is hard to achieve without a plugin. Solutions provided require a lot of administrative and/or manual work. Sometimes a plugin can save you a lot of work (and money); so it might be worth it.

If you're reconsidering the idea of using a plugin, our [Great Gadgets](https://marketplace.atlassian.com/search?query=stonikbyte%20great%20gadgets%20agile) app can be the ideal solution for you.

Danut.


author: Bill Sheboy
body: Hi [@Alexandra Walther](/t5/user/viewprofilepage/user-id/234333)

How do you want to obtain / use that average velocity?

Let's assume you just need the number, perhaps sent as an email with information on the last "N" sprints and the average velocity. And, there are fewer than 100 issues in each sprint.

If so, it would be possible to create a long and slow automation rule, triggered on sprint completion, to send the email. Please note, I have not tried this although I am certain it is possible...and here is an example rule:

* trigger: sprint completed
* action: Send Web Request, to call the REST API to get all of the sprints for the board indicated by {{sprint.originBoardId}}
* condition: check the call worked
* action: Send Web Request, to call the REST API to get all of the sprints for the board indicated by {{sprint.originBoardId}}, and this time filtered to only return the last N sprints by adding the parameters
  * ?maxResults=***N*** \&startAt=**max(0, *the total count from the last call minus N)***
* condition: check the call worked
* *here is the cumbersome / hardcoded part...which is repeated for each of the N sprints*
  * action: lookup issues with JQL to gather the issues in the sprint (by id value) AND which were resolved during the start / end dates of the sprint
  * action: create variable to save the sum of the story points
  * action: create variable to save the count of the issues in the sprint
* action: send email
  * use the variables to average and report the result

A rule like this would be limited to around 20 sprints for N due to maximum rule size, but that seems a bit excessive. It may also be quite slow, and so the service limits should be monitored.

And...I probably wouldn't build this rule for a team I was supporting. One reason is: a lot of things impact velocity, and velocity is not the only indicator of health, progress, value delivery, etc. Building automation for this measure may lend a level of credibility to the measure that is not defendable. Instead, having a team discussion at the retrospective about what the team observes recently and the value delivered may be better indicators of progress and opportunities where the team could experiment to improve.

Kind regards,  
Bill

comments: author: Alexandra Walther
body: Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313)

Thanks a lot for this Idea with the automation., but it's a bit oversized for my usage. As an Agile Coach of a Team I like to support the squad in different ways to improve their delivery.  
The velocity is a number which helps the team to not overload a sprint, but also helps the PO to somehow get an estimation about when a feature of the product backlog might be available in the market.  

As this is a pretty common number in Scrum, I was wondering why it's not available in Jira as a default.  

Thanks a lot for your hint with the automation. I'm pretty sure it will help me somehow in the future!  

Kind Regards,  
Alexandra  

<br />

<br />


author: Shikha Verma
body: **Hey [@Alexandra Walther](/t5/user/viewprofilepage/user-id/234333) You can try Using Jira Filters and JQL**

* **Step 1:** Create a JQL filter for each sprint that captures the story points completed.
* **Step 2:** Use the `SUM` and `AVG` JQL functions (if your Jira version supports it) to aggregate data across multiple sprints. This requires some manual effort but can be an effective way to calculate averages without external tools.

comments: author: Alexandra Walther
body: Sadly it seams as if this JQL filter options are not available in Jira cloud.  
At least I only get all issues listed, but not the number of completed storypoints per sprint.  

Anyhow thx a lot for the support!


author: Shikha Verma
body: You're welcome [@Alexandra Walther](/t5/user/viewprofilepage/user-id/234333)


Tags: cloud

jira-cloud

reports

velocity