Burndowns

Burndown charts graph work remaining vs time. They were originally used for tracking work in Sprints and across releases. Sprint Burndowns that track hours of task work remaining are usually considered an anti-pattern now. Instead, try limiting Work in Progress. Tracking (if required at all) can be done at the level of completed tasks or, better, completed User Stories. Burndowns for release imply the Product Backlog has fixed contents and we’re only releasing every few months. Look instead at a Cumulative Flow Diagram to help improve flow.