About Epics Burnup
Epics Burnup report shows total scope and completed scope on a sprint by sprint based for selected epics. It calculates min, average and max realized velocity of a selected epics and provides forecast dates when the scope of the epics can be completed for each type of the velocity.
Epics Burnup report functionality is identical to Release Burnup report. The only difference is how scope and velocity are calculated.
Scope Calculation in Epics Burnup
In Epics Burnup epic’s scope will be it’s native estimation, not linked stories estimations sum. It allows you to get a burnup without splitting Epics on Stories and estimating those Stories.
Velocity Calculation in Epics Burnup
In Epics Burnup epics realized velocity is used instead of sprints velocity. Epics relalized velocity is calculated based on the progress of stories linked to that epic in particular sprint. E.g. epic has two stories and in the previous sprint one story was completed. Then epics velocity in that sprint equals to completed story size.
Why Epics Burnup is needed?
First of all Epics Burnup simplifies highlevel planning when only estimated epics would be enough to build the burnup because epics native estimation is treated as a scope.
Another advantage of Epics Burnup is the granularity of the burnup report – you can select epics individually and get the burnup report only for them. It is useful to control and monitor large parts of the big projects.
Finally, you will have complete picture on the epics forecast completion dates while splitting epics on stories iteratively, not upfront, because total scope is defined by epics estimation, while the the progress is defined by completed linked stories.