Skip to Main Content

Share your product feedback

Status Future consideration
Categories Releases Sprints
Created by Mark D
Created on May 23, 2017

Burn *Up* charts for Sprints, Releases, Epics, and Features

My company would find it useful to have Burn *Up* charts that show how the effort completed is tracking against the scope of a release / master feature / feature

For more on the requirements for a Burn Up chart and why it is more useful than a Burn Down chart, see here...

http://www.clariostechnology.com/productivity/blog/burnupvsburndownchart

  • Attach files
  • Alex B
    Reply
    |
    Aug 7, 2019

    Our new leadership team prefers Feature level burnup reporting over burndowns. This will force me to obtain this through either TFS or Excel meaning less time that our users will spend in Aha. Hoping that this change is implemented in the near future.

  • Mark D
    Reply
    |
    May 23, 2017

    Although I submitted this in the "Releases" area, it is equally useful for Master Features and Features reporting as well (possibly even more useful)

1 MERGED

Retrospective burnup chart

Merged
Who would benefit? PMO What impact would it make? Leadership report How should it work? Burnup can provide better visibility of development progress.
Guest about 1 year ago in Releases 0 Future consideration