Capacity and Burndown charts - Help required.

[Joby John]

Hi Team, 

I Am new to Jira, and previously was using Azure DevOps. Wanted to find out how do we enter the team capacity for a sprint. Since each resource will work on different hours I wanted to know whether Jira is capable enough of having provision to enter the resource working hours in a sprint. For example. 

Resource A : 7 Hours

Resource B: 3 Hours

Something like this, additionally how do we read the burndown chart right now this is the burndown chart I have, 

The userstories have story points and sub tasks have original estimates and time spent efforts.

I wanted to view how many story points are left for the sprint. I find this graph hard to read... any leads.? :) 

[Dan -minware- · Accepted solution]

Disclaimer: I am a marketplace vendor (marketplace listing)

Hey @Joby John - 

I came across your question this evening and wanted to let you know that minware presents exactly what you are looking for in our sprint insights. 

Here is an example summary of an active sprint (10/3 - today, 10/10) that has 8 tickets / 20.5 points remaining: 

Since you also mentioned tracking estimates and time spent I think you will find our velocity metrics interesting. This example is a task that was estimated to take a day and took slightly longer:

We try to present things as simply as possible so that anyone on your team could lead a data-driven sprint retrospective meeting. 

I saw Walter's response and wanted to present this as another option - hope you find what you are looking for. 

Cheers,

[Joby John]

Thank you 

[Patricia Bermejo]

Hi Dan, 

I am trying to find something similar that you mentioned in your message but unfortunately I cannot find the solution you mentioned.

Please, could you specify in detail the steps to see the board that you have included?

Thanks in advance.

P.B.

[Dan -minware-]

Hey @Patricia Bermejo - we are a 3rd party. Google minware or click the marketplace link in my previous post if you want to learn more about the company.

We have made a ton of updates since that last post - would love to learn more about what you are looking for. 

My email is dan [at] minware [dotcom] if you want to reach out. Let me know how we can help! 

[Walter Buggenhout · Accepted solution]

Hi @Joby John and welcome to the Community!

Your sprint capacity (in Jira, but basically in agile practice) is based on your team's past performance, or its velocity. You will be able to read that velocity from the velocity chart, once you have completed at least one sprint.

Once you know your team's velocity, you will know how many story points, hours or issues you can add to a sprint.

A second thing you should keep an eye on: to get a sensible burndown chart, add all the issues to your sprint before the sprint starts. The red line on your chart goes up on 2 occasions because your team is adding work to the sprint while it is already running.

If you want to track progress on story points, you should make sure to set story points as the estimation statistic on your scrum board settings. Be aware that you will only see a burndown of the story points line when your issues get actually completed (i.e. reach the rightmost column of your board). Your subtasks will not impact the burndown line at all.

For a bit more background, also see this support article on the sprint report and this burndown chart turorial. 

Hope this helps