How to I track Sprint and PI performance by using issues. We do not use story points

[Deepali Dabholkar]

How do I track my sprint and PI performance without using story points. My requirement is % of how we have performed in the sprint and PI

[Alexey Pavlenko _App Developer_]

Hi @Deepali Dabholkar ,

Natively, unfortunately, it's not possible. You can achieve it using the app I developed - Multi-team Scrum Metrics & Retrospectives.

1. Track my sprint and PI performance. You can select Period (X-Axis) between sprints, months, quarters, half-years, or years. If you select a period higher than sprints you can drill down to periods below. Also, you can display several teams/boards on a single view. See screenshot #1.
2. By using issues. You can select Measurement Unit (Y-Axis) between Issue Count, Story Points, Story Point Estimate, Original Estimate, Remaining Estimate, Time Spent. See screenshot #1.
3. Requirement is % of how we have performed in the sprint and PI. There are 9 pre-defined metrics or you can construct any metric yourself using JQL. Also, you can choose to measure throughput or velocity which will be displayed in the chart header. Additionally, there is average and trend of each metric across the number of selected periods.  See screenshots #1, 2 and 3.

A single bar analysis with drill-down from 2024 to H1 2024 - Screenshot #1 (years, issue count, 2 periods, 2 teams/boards):

Summary and trend of all sprints - Screenshot #2 (sprints, story points, 2 periods, 2 teams/boards):

Analysis of one team period - Screenshot #3 (sprints, story points, 2 periods, 3 teams/boards):

There are much more features inside, including quantifiable retrospectives supporting SAFe framework.

Best regards,
Alexey

[Birkan Yildiz _OBSS_]

Hey @Deepali Dabholkar

If you are open to using a marketplace app, Timepiece - Time in Status for Jira can help you achieve this.
To track Sprint and PI performance without using story points, focus on duration-based metrics that identify how work flows through your iterations.

Tracking Sprint Performance
For individual sprints, use the Timepiece’s Status Duration Report. This report calculates the cumulative time an issue spends in each status of its workflow.
Configuration: Use Timepiece’s Sprint filter for your specific sprint (e.g., sprint = "Sprint Name").
Performance Metrics: Group the report by Assignee and select the 'Average of durations' option. This allows you to identify which stages (e.g., "In Progress" or "Review") are taking the most time and pinpoint bottlenecks for specific team members. To learn more about Any Field Duration report, you can check this article out.

Tracking PI Performance
For tracking performance across a Program Increment (which spans multiple sprints), use the Any Field Duration Report. This is a specialized report that tracks the duration a specific field, such as the Sprint field, holds a certain value. Also, you can use the Duration Between Statuses report to measure Cycle Time and Lead Time.

Ensuring Accuracy
To ensure the reliability of your performance data, configure a Custom Calendar. This ensures that your duration metrics (Average/Sum) only count active working hours, excluding weekends and holidays, providing a precise representation of team efficiency. You can also place these reports as Dashboard Gadgets for real-time visibility into iteration progress.

 To learn more about Timepiece, visit its Atlassian Marketplace page.

Disclosure: I am part of the OBSS team, the creators of Timepiece.

Best,
Birkan

[Danut M _StonikByte_]

Hi @Deepali Dabholkar,

This depends also on how you want the progress metrics to be displayed. For examples. if you need burndown charts, a way to do this is to use Jira reports (such as Sprint Report, or Release Burndown) to track by Issue Count. 

But considering that you work in scaled / multi-team environment, my advice is to use dashboards for every team and for the global PI tracking as explained in this article: 

https://community.atlassian.com/forums/App-Central-articles/How-to-track-scaled-agile-SAFe-projects-in-Jira-with-Great/ba-p/1929694

Jira offers some good gadgets, such as Sprint Burndown or Sprint Health, but they are limited when it is about tracking the progress at the PI level

For effective tracking I would recommend using an app from Atlassian Marketplace. In case you want to use an app, our Great Gadgets offers all you need for tracking sprint and PI in an easy & effective way.

Here are some examples:

 Hope this helps.

Danut

[Iryna Komarnitska_SaaSJet_]

Hello, @Deepali Dabholkar !

In general, story points aren’t one of the estimation methods available on your board. There are three options in total:

1. Story Points — best for agile teams that prefer estimating relative effort

2. Issue Count — best for teams whose tasks are roughly the same size

3. Original Time Estimate — best for time-sensitive deliverables

I’ve explained each method in more detail in this article.

The key is to choose the approach that works best for your team. Once you’ve decided, you can start planning your sprints and then evaluate their performance.

If you’re open to using a third-party app, I’d recommend trying the Sprint Report in Time in Status (an app my team built). It lets you analyze completed sprints and includes a Team Velocity chart that compares committed vs. completed work for the last seven sprints, along with an average trend line.

To evaluate an active sprint, you can use the Burndown chart.

We also recently released a new feature that shows exactly what’s included in each metric—for example, which tasks were carried over, added, or removed during the sprint.

Hope this helps!

[Nikola Perisic]

Hello @Deepali Dabholkar 

These articles might be helpful for you: 

https://community.atlassian.com/forums/App-Central-articles/Tracking-Your-Jira-PI-Plan-with-Kendis-for-Atlassian/ba-p/3103370

https://www.easyagile.com/blog/keeping-pi-planning-objectives-on-track-in-jira

Most recommended by Atlassian: https://success.atlassian.com/solution-paths/quarterly-planning-guidance-with-jira-cloud/conduct-a-pi-planning-event/how-to-track-and-manage-program-increment-pi-objectives