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,467,306
Community Members
 
Community Events
177
Community Groups

Can Capacity Tracker sprint cope with partial days?

I've noticed Capacity Tracker has a tendency to be over-optimistic in its tracking for us, and it seems the problem is it can't cope with partial days.  You either get an entire day's worth of hours allocated for a person, or you get nothing. 

If a sprint has only one hour in a day, the tracker still thinks a person can do a whole day's work in that day.

If a day has only one minute left in it, the tracker still thinks a person can do a whole day's work in that day. 

This means the estimates are only accurate:

- First thing in the morning, before anyone's started work.

- Where a sprint finishes at the end of a day. 

The first of these causes capacity to 'yo-yo' around the place, as hours remaining get reduced during the day, but the hours tracked remain the same. Green at the end of the day can be red the following morning. 

The second one is tricky for us, as our sprints finish part way through a day, which means the working day can get counted in both the old sprint and the new sprint, creating non-existent time out of thin air. 

Is there a way to avoid this and have it take into account hours (not just days) in the sprint, and count the passage of hours (not just days) for the sprint time remaining? 

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events