Agile Metrics

Sorokach, Mark D
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 12, 2024

Hello,

I'm trying to find a simplified metrics view that is easy to read and will provide me a review of how our scrum teams have been doing over certain period.  I was hoping there is an option to have a few charts that give Average % of Planned Velocity Accepted, Average User Story Cycle Time, Epic Lead Time, average planned velocity, average velocity, user story throughput, user story accepted points, average story size, test defect ratio and defect type breakdown.

7 answers

1 accepted

2 votes
Answer accepted
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
December 12, 2024

Hi @Sorokach, Mark D -- Welcome to the Atlassian Community!

In my opinion, some of the measures you note are not "simplified metrics" and also unlikely to be found in the basic, Atlassian interpretation of measures for Scrum teams.

Perhaps start by viewing what is in the built-in reports and dashboard gadgets, and any possible configurations to the Atlassian interpretation of a Control Chart and Cumulative Flow Diagram to find the time-based and count-based things you note.  Then consider what you want to measure (and why those things) and then check the Atlassian Marketplace to identify addon apps / gadgets to help.

Kind regards,
Bill

Sorokach, Mark D
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
December 13, 2024

Thank you for your help @Bill Sheboy

Like Bill Sheboy likes this
1 vote
Vitalii_Bobak_SaaSJet
Atlassian Partner
December 16, 2024

Hi @Sorokach, Mark D 
Welcome to the Community!

For metrics like Average % of Planned Velocity Accepted, Average User Story Cycle Time, Epic Lead Time you can try add-ons like Time in Status or Time Metrics Tracker


With Time in Status you can easily get metrics like Cycle Time, Lead Time Report

Frame 1021.png

Or Average Time report 

Знімок екрана 2024-09-19 о 20.53.57.png
Also you can display all of this by Charts View. 

Знімок екрана 2024-09-19 о 20.55.23.png
Another option can be
 Time Metrics Tracker. This add-on breaks down transition times between statuses in a more straightforward way, making it easier to track your team's efficiency and spot bottlenecks. Plus, it provides flexibility with exporting data and setting custom time metrics.

image.png

I hope this helps!

You can also book a live session or contact us at Support - we'll help you with add-ons. 

Add-ons developed by my team.

0 votes
Mehmet A _Bloompeak_
Atlassian Partner
December 18, 2024

Hi @Sorokach, Mark D

Welcome to the Atlassian Community!

Cycle time and lead time raw data is available in issue history and you can get it using Jira Rest API. It provides status changes for each issue by returning a json which you need to parse to calculate cycle time and lead time.

If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Cycle Time for Each Issue and Lead Time for Each Issue reports. You can choose the statuses that you want to include in cycle time and lead time calculation.

For further details, you can have a look at Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters article and Status Time Reports How to Videos.

App Features:

  • This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).
  • You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
  • Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
  • You can set different duration formats.
  • You can export reports in CSV file format and open them in MS Excel.
  • You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
  • You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

If you have any questions, feel free to schedule a call with us.

Hope it helps.

0 votes
Rahul_RVS
Atlassian Partner
December 17, 2024

Hi @Sorokach, Mark D 

Welcome to the community !!

For calculating cycle time for your issues, if you would be interested in a mktplace app you can try out

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. You can group your statuses ti define your own cycle / lead times. This app also can easily be added as a dashboard gadget.

More details here.

Disclaimer : I work for the vendor who built this appTIS - Cycle Time report.PNG

0 votes
Gizem Gökçe _OBSS_
Atlassian Partner
December 16, 2024

Hello @Sorokach, Mark D ,

Welcome to the community!

For the metrics you're looking to review—such as Average User Story Cycle Time, Epic Lead Time, Average Velocity, and User Story Throughput—you can use a 3rd party reporting tool such as Timepiece - Time in Status for Jira , developed by my team, to generate these insights:

  1. Define the Metrics:

    • You can calculate these metrics using Average Reports in Timepiece.
    • For example, you can define the duration between specific statuses (e.g., "In Progress" to "Done") to calculate the User Story Cycle Time or Epic Lead Time.
  2. Group by Time or Sprint:

    • By grouping the data by Date or Sprint (Latest), you can observe trends over time or across sprints.
    • This will provide a simplified and clear view of your team's performance over the desired period.
    • Average Sprint Report.png
  3. Visualization and Export Options:

    • Timepiece includes built-in visualization options such as Column Charts, Bar Charts, Line Charts, and more. These visualizations make it easy to analyze trends and share results with stakeholders.
    • If needed, you can export the report data to formats like CSV or XLS for additional customization or presentation.
    • Graph Sprint.png

Timepiece offers flexibility in creating custom reports tailored to your needs. If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features.

Hope it helps,

Gizem

0 votes
Alexey Pavlenko _App Developer_
Atlassian Partner
December 15, 2024

Hi @Sorokach, Mark D ,

Natively, you can get

  • User story accepted points (Committed) via the Velocity Report
  • User story throughput via JQL and use some native gadget to visualize it
  • Average velocity - calculate manually from the Velocity Report
  • Average User Story Cycle Time - calculate manually from the Cycle Time Report, but you will need to set it up first

For all other metrics, you need to use 3rd party apps.

To collect and visualize at least half of the desired metrics, you can use the app I have developed - Multi-team Scrum Metrics & Retrospective. With it, you can visualize and track 9 pre-built metrics or any custom metric constructed via JQL over any period - sprints, months, quarters, half-years, or years. Also, you can drill-down them or retrospect them in place.

Screenshot #1

Screenshot 2024-12-13 133956.pngScreenshot 2024-12-13 161807.png

Screenshot #2

Screenshot 2024-12-13 174717.png

 

Screenshot #3

Screenshot 2024-12-13 195809.png

Best regards,
Alexey

0 votes
Danut M _StonikByte_
Atlassian Partner
December 14, 2024

Hi @Sorokach, Mark D,

My advice is to use Jira dashboards to create such view(s). They have the advantage of being customizable and centralizing all the information in one place. In addition, they can be shared with other users.  

Jira offers some useful agile gadgets (such Sprint Burndown Chart or Sprint Health Gadget), but for a complete coverage of the metrics that you mentioned, most likely you will need to search on Atlassian Marketplace for a plugin that offers the gadgets that you need. 

In case you want to try a plugin, our Great Gadgets app offers a complete suite of gadgets for tracking agile projects. I think it will allow you to easily track all the metrics that you mentioned. 

Take a look over these articles to make an idea:

If you need any help with the configuration of these gadgets, feel free to contact our team at support@stonikbyte.com.  

Danut

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events