Where does the Burndown chart get "actuals" Story Poindata to compare against Estimate Story Points

Question

Where does the Burndown chart get "actuals" Story Point data  to compare against Estimate Story Points

Example

ISSUE 001 - original Estimate 5 points

Some work gets done and there are 3 points remaining

Some more work gets done and there are 0 points remaining

How does Jira capture the progress on the project?

What does the developer need to do in Jira to reflect their progress?

Nic Brough -Adaptavist- · Answer

That is correct, yes.

In an ideal world, you don't change a stories points during a sprint (nor do you add or remove stories in the sprint).  In real life, these do happen and Jira reflects it as scope change - the idea of the sprint is you say "we commit to doing X", so changes to stuff in flight changes your committment.  But the sprint doesn't care if estimates are changed before the work is started, so that's not really looked at.

Scott Barnard · Answer

Hi Nic

Thank you.  So if the Issue scope changes up or down, that can be reflected on the story, but best practice in Jira then is to leave the points alone if nothing changes and let the "done" tell the tale.

Nic Brough -Adaptavist- · Answer

There is no "actual vs estimate".

The burndown works off stories being "done".

You put an estimate on the story.  When you move the story to the far right column on the board, it is done, and the points currently on the issue (which you might have changed) are then used.  Whatever the value is at that point is the "actual".