Calculating "Averages" using Custom Values or JQL Expressions

[Isabella Musial]

I was trying to use Calculations to do the math to get the team average (yes, Velocity) for each individual member of the team - just to use as a baseline so we do not overburden anyone (all internal).  

This is what I came up with - but I cannot figure out how to 'count sprints' instead of using days. This way, it's now always accurate.

Is there a way to 'count sprints'?

issueFunction in expression("filter = 73766", "StoryPoints / 33d")

Filter 73766:

issueFunction in aggregateExpression("Total Story Points", "storyPoints.sum()") AND status in (Closed)

I also tried Custom Values but the numbers are WAY off.  I am using Rich Filters to show only my current Increment. 

 what am I doing wrong here? 

thanks for your help! 

Bella

[Danut M [StonikByte] · Accepted solution]

Hi @Isabella Musial,

Counting sprints, most likely, will not be possible. But, if you have sprints of a fixed length, you could divide this by a number representing the number of sprints that fit in the 33 days (if your sprint has 2 weeks, you could divide by 3 instead of 33), thus obtaining a "per sprint" velocity instead of "per day" velocity calculated as the average of past 3 sprints.

Be aware that there might be better alternatives to your current method. For example, you could also try these two gadget offered by our Great Gadgets app. But, again, both will calculate per time interval, not per sprint. 

Advanced Issue Filter Formula gadget

Kanban Velocity gadget -  in this case, you will need a gadget for each team member

Hope this helps.

Danut.

[Isabella Musial]

This is great thanks! Even better.... we have those gadgets and I was not even aware! I'll try those, too! 

[Isabella Musial]

@Danut M [StonikByte]  I am looking at the help doc, but I am a little stuck at how to do the calculations. Do you have a screenshot you can share of the velocity by Team Member? 

[Danut M [StonikByte]]

Hi @Isabella Musial,

Please contact our support team at support@stonikbyte.com and someone will get in touch with you right-away.

Thank you,

Danut

[John C · Accepted solution]

It's a crude approach, but one way would be to modify your expression above to divide by X calendar days instead of the 33 days you have above?  ie divide by 14 days to get a two-week Sprint average?

You could also search for all the issues a developer has completed in a given Sprint and sum the number of story points Done.

You can expand this and add a dashboard gadget based on all of the developers in the team that would present developers on one axis and Sprints on the other.

Having suggested these, I also have a responsibility to mention that velocity is meant for tracking Scrum team performance and I would normally discourage tracking velocity down to an individual developer...

Good luck!

[Isabella Musial]

Thanks!!! I totally agree - Velocity is team based. And thanks for the suggestions! 

We are trying to solve an issue if individually we have to much work per person since most of the stories on this team aren't a "team" effort. It's a weird setup, but we are being "agile" and trying something to see if it works ;) 

it may be a bust, who knows!