nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Sprint Burndown Stops Before End of Sprint

JD_2d69iu

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

Accepted answers

All comments

Jack Nolddor [Sweet Bananas]

JD,

It seems the Sprint was scheduled to run until 21/jan but was closed a day before that's the reason the red line stops/has a gap with a day to go and the graph doesn't touch the rightmost side.

Regards

JD_2d69iu

Hi Jack.

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

JD_2d69iu

Broken Burndown 2.png

Jack Nolddor [Sweet Bananas]

Estimation needs to be done before the Sprint starts, if not i will be consider as Scope Change.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

burndown