Capacity Planning - by Individual

[Jamie Stanczyk]

Good afternoon everyone! After several hours of searching, I thought I would ask the question here about putting together reporting for our teams.

Within our Jira Instance, we have company-managed scrum projects and have the ability to use Plans as well. We are in the process of possible moving to teams for each Jira project, instead of products for each project.

While going through all of the project-based reports and creating custom dashboards, I cannot find the ability to report out on individual story point based reports. Here are some examples:

• Average Developer Capacity - on average, how many points is the developer committing to each sprint
• Points Completed - on average, how many points is the developer completing each sprint?

I even tried creating custom filters to funnel into the dashboards, but with story points being a difficult field to measure in dashboard reports, I cannot find a way. A lot of research points me to having to use an additional plug-in/marketplace app, but I wasn't sure if this was possible without.

[Rahul_RVS]

Hi @Jamie Stanczyk 

If you would like to try a mktplace app for tracking resource workload and capacity planning across multiple projects/boards, take a look at

Capacity Planner 

The app offers:

1. Resource Tracking and Allocation : The app allows you to monitor and track various resources by adding them as part of a template, and their work allocation across multiple projects / sprints.

2. Real-time Visualization: Provides intuitive charts, graphs to visualize resource utilization and capacity levels in real-time.

3. Full Sprint / Project Fix version Capacity and Monitoring

Mode details here

[Daria Spizheva_Reliex_]

Hi @Jamie Stanczyk ,

If you don't mind exploring a marketplace app with some workaround, then ActivityTimeline can help with your needs. You'll need to set up a Story Point-to-hours conversion rate in settings, which allows the tool to calculate workload based on your Story Points estimates.

Once configured, you can use custom reports like the Resource Utilization Forecast to see each developer's expected workload per sprint, and the Planned vs Actual Chart to compare scheduled effort against actual delivery - both will show the data in converted hours.

While the reports won't display the raw Story Points numbers, you can interpret the hours back to Story Points using your conversion rate. For example, if you set 1 Story Point = 8 hours, and a developer shows 40 hours of capacity, that translates to 5 Story Points. The Detailed Worklog Report can also show you completion data in hours, which you can convert back to understand how many Story Points were actually completed per sprint.

Let me know if this would be helpful.

[Dave]

Hey @Jamie Stanczyk 

This is a topic I'm particularly interested in and have built an application that is freely available on the Atlassian Marketplace called Sprint Capacity Analysis

However, one thing it doesn't do is report on what individuals have done and I'm really keen to understand why this is a requirement. Obviously all teams are different but would you not expect team members to collaborate to complete tasks rather than working in silos?

For example with peer review processes there is often a case where code changes can't be merged without one or two other team members reviewing. You might also have the situation where senior team members are mentoring more junior members so even though they aren't the assignee they are directly contributing to the work item outcome.

Personally I like to think of scrum as a team sport and that the team only succeeds when they collaborate together. I'd always be cautious that measuring individual metrics like this can lead to a lack of collaboration.

Obviously your situation might be very different so I'm really interested to learn how you'd use this data to help with planning - any insights you can share would be really useful for me!

Many thanks,

Dave

[Iryna Komarnitska_SaaSJet_]

Hi @Jamie Stanczyk ,

Thanks for raising such a relevant question—reporting on individual capacity using story points can indeed be challenging in native Jira, especially across multiple projects or teams.

If you're open to using a marketplace app, I’d recommend looking into the Sprint Report feature in the Time in Status app by SaaSJet. While it's not a full capacity planning tool just yet, it does offer some useful metrics that can support your analysis.

What it provides:

• Workload by Assignee: A per-sprint breakdown of how many story points (or original estimates/counts) were committed, added, and removed per individual.

• Completed Work: Tracks how many story points an assignee completed in each sprint.

• Velocity Charts: Shows overall team velocity trends over the last 7 sprints, which helps approximate average delivery pace.

What it doesn’t do (yet):

• It does not calculate average developer capacity over time automatically across sprints. However, by reviewing multiple sprints in the velocity and workload sections, you can manually estimate this value per developer.

• It does not include forecasting or planning against future sprint capacity per individual—but we’re actively collecting feedback on this use case.

So while we can't provide full capacity planning at the individual level yet, this report can give you a solid foundation to analyze trends in committed vs completed story points per person.

But alternatively, I can offer to generate reports on the workload of individual Assignees in pivot tables in the Time in Status app (you can add any fields to the calculation, including story points and number of tasks).

If you'd like, I can share a sample view or walk you through how to use it effectively for your case.

Let me know if this would be helpful.