Scrum burndown charts

[Rithuja]

I am managing an Agile project using service now. I would like to know how the burn down charts are getting updated in service now. We update the status of each story depending on the progress daily from ready to in progress, ready for testing. But the burn down chart shows a straight line throughout the sprint and then drops only when it is marked as complete. 

I would like to know how the burndown charts can be updated based on the daily progress.

[sachin_namjoshi]

The Sprint Burndown Chart pulls from the 'Story Points' field on the Sprint form. The chart pulls when the Sprint is NOT in 'Draft' or 'Planning' state. A new plotting point is plotted on the Burndown Chart whenever stories (and therefore Story Points) are added or removed.

This 'Story Points' field pulls from the 'Points' field on the Story forms for all stories within that sprint.

The code for rendering the Burn Down Chart is in a Script Include, BurnDownUtil:

sys_script_include.do?sys_id=c7409b7237131000913e40ed9dbe5d6f

The BurnDownUtil code renders the chart using the following information:

1) The planned start date and planned end dates of the release correspond to the time period for the chart.

2) The chart looks for RM Release Total Story Count metric instance records for the release

...2a) There needs to be at least one of these records, or the system reports there is not enough data to draw the chart

...2b) There can be more than one of these records because this becomes a record of the total story points (as stamped in the start time of the metric instance record)

3) The RM Story State Capture metrics are records of when a story is completed; the story points are deducted from the total remaining points, and a line is drawn from the last previous total to the new total."

Regards,

Sachin

[Rithuja]

Hi Sachin,

Thanks for the response. The story is marked as complete mostly towards the end of the spring once testing is completed by the business users. Once development and unit testing is complete, the developer marks as ready for testing. 

Testing by business users will be done only 2 or 3 days before the end of sprint and so the burn down chart is mostly a flat line and then it drops suddenly. Is there any way to change the burn down chart based on the status change by developer.

[AC333]

Any update to this? We have the same situation and want a burndown chart based on remaining hours decreasing, not story state changing to completed. Is there another option other than the OOB sprint burndown chart?

[Tara Z]

Same here, any update?  Stories are not marked complete until after UAT is complete and the code is deployed.  From a dev perspective, the work is complete but the burndown chart does not move until after code deployment is complete which is not an accurate representation of actual work completed during the sprint.