Determine average size of upcoming and completed tickets

[Alex Jordaan]

Within the new team I have picked up I am trying to determine the average sizes of tickets that have been completed or are upcoming. 

Within the current sprint I have noticed some very big tickets (21) points, and am trying to understand the sizing allocations in previous sprint velocity is skewed by these huge tickets. 

I would like to normalise the ticket sizing as the team is quite new and junior. 

Any ideas on how to query/determine in a dashboard the distribution of tickets sizes and the averages?

[Dan -minware-]

Disclaimer: I am a marketplace partner! (marketplace listing)

Hey @Alex Jordaan -

I came across your post this evening and thought you might be interested in our ticket flow report. We try to make our visualizations very easy to understand so the line thickness you see below is based on points associated with the ticket.

What I've boxed in red is a ticket worth 8 points and in purple I am pointing to a smaller line that represents a ticket worth 2:

This is one of the ways that we make it easy for you to understand work in progress and here's what the aggregate view looks like for all ticket in a sprint, accompanied by a burn-up chart:

Hope this helps and you find what you are looking for.

Cheers,

[Marlene Kegel - codefortynine]

Welcome to the community, @Alex Jordaan.

I am Marlene from codefortynine.

With our app Quick Filters for Jira Dashboards you can display the average of story points (or any other Jira number field) on your dashboard.

In the screenshot below you can see as an example the "Quick Issue Statistics" gadget. It is also possible to create statistics for Jira number fields with the "Quick Two Dimensional Filter Statistics" and "Quick Pie Chart" gadget. 

Of course you can also create statistics for any other Jira fields like issue type, status, assignee, component, ... .

[Walter Buggenhout]

Hi @Alex Jordaan and welcome to the Community!

Out of the box, you can't. But if you create a JQL search that has all the data you want to assess, make sure you select story points as a column in the search results. Then export your data to csv and analyse them with Excel.

From an agile perspective: don't do this. I mean, normalising the ticket sizing. At least don't impose this on the team. Rather let them see how velocity varies between sprints and let them participate in finding out why this is happening. Let them come up with suggestions on how to improve (splitting certain huge bodies of work in smaller ones will most likely come naturally from those discussions).

Hope this helps!