Loading Profile...
Why does the burndown chart stay at 0 hours in a 346 hour sprint?
We ("cadia") have been working on our first sprint for over a week now, which we planned without any problems. Our Sprint Backlog summary says "Total: 7 items, 0 not estimated, 75 SP, 13 tasks, 346 h", which is correct. However, the Burndown Chart shows both the ideal burndown and hours remaining as a flat line at 0 hours. What do we have to do to make this chart start at 346 hours and track burndown from there?
I’m perplexed
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
The best solution from everyone
-
We're after release and bugfix for your problem, so there shouldn't be any more problems with burndown chart.
The company and 1 other person say
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?This is really strange. We're investigating this problem. -
Inappropriate?The first thing you have to check is whether the current date is within a boundary of the sprint you mentioned. Be aware of the fact that the burndown presents hours remaining in respect to time -- so when estimates are modified after the end of the sprint or before the beginning, the chart doesn't change.
If this is the case, you can correct the start and end dates of the sprint. If this doesn't solve your problem, tell us! -
Inappropriate?I double-checked and the dates of the sprint are correct. In fact, I get the correct count down towards the end of the time period: E.g. "Current sprint, ending on 13-06-2008 (in 3 days)". I admit I have never used Scrum before, so maybe I'm missing something trivial - but I watched the entire screencast a couple of times, and didn't spot anything. I have been very impressed by how easy this is to use! :)
I’m unsure
-
Inappropriate?Thanks for your report. We have found a bug in sprint backlog burndown. It seems that if tasks were estimated before sprint started, they're not counted in. We have fixed it, but due to our release policy, our servers will be updated at the end of this week.
If this bug is so annoying that you can't wait till Friday, you could try to change start day of this sprint (if it's not overlapping with another one in project). -
Inappropriate?We're after release and bugfix for your problem, so there shouldn't be any more problems with burndown chart.
The company and 1 other person say
this solves the problem
1 Comment Add a comment
This solves the problem
-
Of course please let us know if the problem persists. -
Inappropriate?Hannes, we would be grateful to know whether your problem is resolved by the fix Tomek mentioned or not.
-
Inappropriate?Hi again. Sorry about the delayed reaction, but we just had a long weekend (due to our independence day yesterday). Yes, everything seems to be working fine now! Thank you very much. I appreciate the prompt replies and quick fix!
I’m thankful
EMPLOYEE
