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,463,960
Community Members
 
Community Events
176
Community Groups

Team capacity in the ongoing sprint

Edited

Hi,

I've noticed that when viewing ongoing sprint form the advanced roadmaps "Allocated hours" reduces every day as the remaining estimate decreases though total capacity does not change. Is this functionality as intented or I am missing something?

It might be misleading viewing it after the sprint is started, as it does not account for the remaining capacity as the sprint goes on while taking into account remaining work.

For example:
Day 1; 200/200 100% full
Day 2 160/200 80% full

capacity.PNG

1 answer

1 accepted

0 votes
Answer accepted

Hi @Svajunas Gaina,

Yes, I believe this works as intended. In scrum, a sprint is planned ahead and the amount of hours / story points committed to is - by the book - not supposed to change either during that sprint. If your team follows this practice and does not add additional work after the sprint was started, the commitment / capacity balance during the sprint and your long term planning should not be impacted by the fact that time progresses.

Hope this helps! 

I've tested functionality with test project more in depth and I realized that 117/200 is the remaining/total work added to the sprint. I thought that total was the sprint capacity.

Thanks for your answer though!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events