Burndown Charts are often associated with Scrum, a development methodology known for incremental releases and a focus on customer requirements. As an agile workflow tool, they help teams meet deadlines more predictably by providing an early indicator of how a project is coming along.
Because they provide a visualization of complete and remaining work, they're also a user-friendly reporting tool for GitHub project management.
Burndown Charts are meant to track velocity during short sprints of work – and as such, they are integrated directly with your GitHub milestones. You'll find your team's Burndown Charts in the Reports tab.
To build your chart, you'll need to choose the milestone start and end dates (find the edit link at the top of the chart.) After choosing a milestone, all the issues which have been estimated will be shown.
Just like kanban boards and epics, Burndown Charts can help you visualize projects across repositories. To create a multi-repository Burndown Chart, you'll need to start by connecting repos on the task board. You'll then see the connected repositories listed at the top of the chart, and any merged milestones will appear together as one.
By default, Burndown Charts display closed issues and pull requests as data points. You can also customize which pipeline triggers a “burned” task by using the Burn Pipelines dropdown menu. For example, if your development team considers a task complete when it reaches the “Ready for QA” pipeline, they can set that here for a more accurate picture of their priorities and progress.
- How to save hours per week with ZenHub's additional features