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,555,109
Community Members
 
Community Events
184
Community Groups

Integrate team capacity in JIRA

Hi geeks,

I am working on teams available capacity for a time period (3 sprints/6 sprints/PI/mini PI) vis-a-vis Features we receive from PDM. Is there a way we can configure, team wrt their availability?

Lemme say, 5 members, I consider 75% of their time each day for JIRA accomplishment.

The tool should give me 5*0.75*10days= 37.5 mandays . I can define it as 15SP (each sp=2.5 mandays for my project)

At the end, I can map the EPICs against this available 15SPs.

This is the general idea. Can some one let me know if you have ever done this?

 

Regards

Satya

2 comments

Deleted user Sep 27, 2022

@satyaprakash.mittinti  look I think he's taking the wrong approach, you don't calculate a person's availability as if it were flour to be dosed to make grandma's cookies ...

Jimi Wikman
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.
Sep 28, 2022

What you are referring to is capacity planning based on availability, which every team must do every sprint.

The calculation should also take into consideration things like holidays, vacation and risks like sickness if the flu is going around to set the expected time available. You also factor in how much the team get disturbed, be sitting in open spaces or being dragged into meetings. Most teams are effective at around 50-70% at the most.

So 75% in your case sounds a bit optimistic, unless you never talk to eachother, don't have meetings and everyone is isolated and fully focused ;)

I don't see the point of using arbitrary values like story points as you already translate it to time, but that is up to you :) I would just use hours as that is what you need to keep track of anyway.

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events