I am looking to start using the advanced roadmap \ plans (sprint capacity management view)
using hours as the measure and estimating tasks in hours
and am expecting to get these 2 benefits
setting team capacity in hours for the sprint
- when planning a sprint as each issue issue into the sprint - the team capacity is filled and it shows when the capacity is exceeded by adding a story
- when sprinting I was expecting
- the hours logged against tasks to reduce the teams capacity
- when tasks take longer than original estimates or are re estimated the teams capacity to be reduced accordingly - e.g. I have a task estimated at 10 hours I book 8 hours to the task and estimate the task as having 4 hours remaining
- in this case I expect that the capacity of the sprint will be reduced by 8 hours as this has been used and the allocated hours will be reduced by 6 leaving reducing the amount of free unallocated hours by 2 (as the work has increased from 10 to 12 hours)
- What seems to be actually happening is almost the opposite
- the capacity stays as it was originally entered and the amount allocated is reduced by 2
- this then shows the sprint as having more space rather than less space
- so as the sprint goes on it looks as if its almost empty and we could add more stories