We have a sprint burndown chart for a recent and closed sprint which does not burn all the way to the end of the period - it stops/has a gap with a day to go and the graph doesn't touch the rightmost side.
We had a lot of issues marked as done and some scope changes. We also had some incomplete issues which were moved to the next (current) sprint. Finally, some issues were removed from the sprint, all of which have now been marked as done except one (an epic, which stretches across multiple sprints and should not have been included in this sprint).
Do you know why the chart stops, how to fix it and why it happened/how to prevent it from happening in the future
Image link (trimmed) here: https://img42.com/EyXrP
This seems to be the issue! Thank you. And to convey my thanks, I have a quick follow up question, related to the burndown chart... :l
We add in estimates before the sprint begins e.g. estimates are added at 2pm on 27/01/2020. Then the sprint is started (retrospectively) as of 9am on 27/01/2020.
This leaves the burndown chart starting at zero for a few hours, then quickly spiking to the total of the estimates before burning down as the team add time. No stories are added after the sprint is started.
Is there a way of getting the burndown chart to start at the total of the estimates rather than at zero?
We normally plan our sprint on sprint day 1, so we don't have estimates ready at 9am on sprint day 1; only after the planning has been done
It is my understanding that a new sprint starts at say 9am. The first item on day one of the new sprint is sprint planning, where planning and estimation of tasks are done.
How can the estimation be done prior to the new sprint starting?
Or would you do sprint planning and after that is complete with all estimation finalised, mark the new sprint as started e.g. at 2pm?
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event