Sprint burndown calculations by StorytPoints not by estimated time or efford
Added by Marcin D about 9 years ago
Hi,
I would like to have oportunity to calculate Sprint burndown not by time spend on it but by burned Story Points (like in Product backlog). User story is completed when all sub-task are completed so when all user stories are completed Sprint is completed.
I'm not a fan of strict estimation of time and this is very anoying to calculate efford by time (it's not working for my team).
Were is speed of a team in this kind of calculation?
My proposition is to build chart "Sprint burndown" but StoryPoints by Sprint days. When user story is burned chart is going down and when there is a new user story in sprint chart is going up.
What do you think?
Replies (3)
RE: Sprint burndown calculations by StorytPoints not by estimated time or efford - Added by Anonymous about 8 years ago
I agree on this matter. We should at least have the option to choose between story points / time estimated.
RE: Sprint burndown calculations by StorytPoints not by estimated time or efford - Added by Carlos Jiménez about 8 years ago
I agree with you. This idea for feature would be very useful for us too because we use user stories and subtasks.
RE: Sprint burndown calculations by StorytPoints not by estimated time or efford - Added by Stina Nyman over 7 years ago
I agree too!