Iteration burndown by points, not hours

Discussion created by EricNash Employee on Jun 8, 2017

This is more of a discussion than a question... is my company the only one that would like to see iteration burndown charts by story points in addition to task hours? Most of my teams don't use tasks but there's something to be said for using burndown instead of burnup. Both charts can answer the same fundamental question... how much work is left? The advantage of burndown is that it shifts focus to the amount of work remaining, which I think has a subtle but clear psychological benefit vs. the endless "hill climb" of the burnup chart. The scope line on the burnup chart is OK as a representation of the goal but there's something to be said for working downward until zero work remains.


Anybody have a different perspective on this or a suggested solution for getting an iteration burndown chart without having to use tasks?