Agile, SAFe dashboards BurnUp/ BurnDown chart FAQ's

[Syed Azam]

Below are the frequently asked questions regarding Agile/SAFe BurnDown/BurnUp charts : 

Q. BurnDown/BurnUp charts does not display data in the dashboard:
A. It could be due to one (or more) reasons as mentioned below:

1. Scheduled job “[Scrum] Daily Data Collection” is not active/not run
2. Planned /Actual start dates (as applicable, ref. below table) are empty.
3. Planned /Actual start dates are future dates (whose data is not collected yet).

Epic/Release	Actual start date
Sprint	Planned start date

Q. Job is run but PA indicator doesn’t show the scores for the release/sprint/epic as expected.

A. There are no stories under the selected release/sprint/epic. (or) the underlying stories points are empty.

Q. Only scope line is visible in the chart, no actual burndown/burnup line is seen.
A. It could be because, there are no Stories being completed in the selected sprint/release/epic, “where sum of story points of all stories equals the sum of story points of active stories”, Hence causing Scope line to override the actual line.(i.e: Actual line is hidden by the scope line).

Q. Can the BurnDown/BurnUp charts be plotted for the historical entities. (like existing Sprints/epics/release.)
A. No, BurnDown/BurnUp charts can only be plotted for the sprints/release/epics, which are not complete at the time of activation of the scheduled job.

Q. How are the Scope/Actual forecast values derived for the Scope/Forecast lines?

A. These are the forecast scores provided by the PA indicators corresponding to the respective dashboards.

Q. How can we customize/Override the OOB functionality of BurnUp/ BurnDown charts?

A. OOB functions can be overridden in the respective Implementation classes of BurnDown/BurnUp charts.

For Ex: _generateScopeForecast method can be overridden in ScrumBurnupImpl to override the behavior of ScrumBaseChart for BurnUp charts.