On our burndown chart, it seems that we can't get any points to reduce during our sprint, even though we log time against the story. Is there a way to reduce the burn down remaining by work in progress, if we alter any of the values ? I expected the logged time to help reduce the story points remaining, and not have to entirely complete the story before we would see impact on the burn down.
Thanks for your prompt reply Nic. But shouldn't you have a way to track progress on a particular story during the work in progress ? I'm not suggesting to change the points, but instead consider the time logged on the story to show you are x% complete , and possibly bring that to the kanban board display in a status bar or such ? or be able to represent it on something like the burn down chart ... ?
You could track the progress by having a "part complete" type field, or estimating in time and logging work, but that's not what a burndown works on. The chart works on the things completed in the sprint. If you do the "how complete is this" thing, it's fine, and there are some other reports that can help you visualise it, but it is, by definition, not a burndown chart.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs