Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,560,407
Community Members
 
Community Events
185
Community Groups

JIRA Structure Resource Usage

Does anyone know how Jira decides if a resource is booked for too much work? I understand that more points means more of their effort is required, but doesn't that mean that Jira then assumes that a certain amount of points always takes a certain amount of days to accomplish? Does it take into account past sprints? I am using points to measure the velocity of my team, and also percentage as an indicator for how much work each developer is tackling. I am trying to figure out the resource usage is calculated on the back end - any ideas?

Thank you,

Yuta

1 answer

0 votes
Ignacio Pulgar
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.
Jun 29, 2020

Hi @Yuta Nagano ,

It's a good question, as the calculations for obtaining velocity are not intuitive.

First, let me clarify that Jira does not assume any conversions from Story Points into time.

The Velocity Chart is calculated by taking the average of the total completed estimates over the last several sprints.

More information on how to understand the Velocity Chart:

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/

Hope it helps.

Suggest an answer

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

Atlassian Community Events