Zenhub Blog > Project Management > Track Velocity on GitHub Repositories with Multi-Repo Burndown Charts Zenhub Blog > Project Management > Track Velocity on GitHub Repositories with Multi-Repo Burndown Charts Project Management Track Velocity on GitHub Repositories with Multi-Repo Burndown Charts The Zenhub Team March 23, 2020 | 1 min read Editor’s note: This blog post was originally published in March 2016 and has been completely revamped and updated for accuracy and comprehensiveness. For project managers, tracking progress toward upcoming releases is crucial. But when projects span several GitHub repos (as they often do), seeing the whole picture can be difficult. With Multi-Repo Burndown Charts, teams can track progress across repos. This provides teams with a complete visualization of all completed and remaining work within a sprint. Here’s how to get started: 1. Connect repositories into one Zenhub Workspace Multi-Repo Boards are a simple way to track issues from several repositories in one place. Click here to learn how. 2. Create a sprint Burndown Charts are meant to track velocity during short sprints of work – and as such, they are integrated directly with your Zenhub sprints. Hit the + icon beside the ‘New Issue’ button to create a sprint spanning repositories: Once you have created your sprint with a start date and end date, navigate back to the Board. You can use multi-action to select multiple (estimated) Issues to be added to the sprint. Click here to learn more. 3. Navigate to your Burndown Report Your Burndown Charts can be accessed via the ‘Reports’ section in the sidebar of your Workspace (or by using the keyboard shortcut z + d). The repos you’ve connected to your Multi-Repo Board will appear together here. You can check or uncheck repos to filter your Burndown Chart. 3. Select a sprint Choose a sprint from the drop-down filter on the right. Zenhub burndowns will be available for the last 10 closed Milestones. You can also export the report to CSV to further customize and analyze data. 4. Track your progress! After choosing a sprint, all Issues which have been assigned a story-point estimate will appear on the Burndown Chart. As you finish Issues assigned to the Sprint, a new data point will appear, "stepping down" in the chart. You can also check out our help article for more information on Burndown Charts! Questions? Ideas? Shoot us an [email](mailto: support@zenhub.com) or chat with us on Twitter! m Share this article New Work smarter, not harder. With Zenhub AI Simplified agile processes. Faster task management. All powered by AI. Learn more
Project Management Engineering Team Efficiency: Getting the Most Value from Project Management Tools Chaissan Ashcroft December 18, 2024 | 5 min read Productivity Zenhub Sub-issues: The Ultimate Guide to Aligning Strategy and Development Tasks Chaissan Ashcroft December 16, 2024 | 7 min read Project Management Why Engineering Teams Are Moving Away from GitHub Projects in 2025 Chaissan Ashcroft December 12, 2024 | 6 min read Project Management The Hidden Costs of Using Jira for Software Development in 2025 Chaissan Ashcroft December 11, 2024 | 8 min read Hone your skills with a bi-weekly email course. Subscribe to Zenhub’s newsletter. Email Return to top
Productivity Zenhub Sub-issues: The Ultimate Guide to Aligning Strategy and Development Tasks Chaissan Ashcroft December 16, 2024 | 7 min read Project Management Why Engineering Teams Are Moving Away from GitHub Projects in 2025 Chaissan Ashcroft December 12, 2024 | 6 min read Project Management The Hidden Costs of Using Jira for Software Development in 2025 Chaissan Ashcroft December 11, 2024 | 8 min read Hone your skills with a bi-weekly email course. Subscribe to Zenhub’s newsletter. Email Return to top
Project Management Why Engineering Teams Are Moving Away from GitHub Projects in 2025 Chaissan Ashcroft December 12, 2024 | 6 min read Project Management The Hidden Costs of Using Jira for Software Development in 2025 Chaissan Ashcroft December 11, 2024 | 8 min read
Project Management The Hidden Costs of Using Jira for Software Development in 2025 Chaissan Ashcroft December 11, 2024 | 8 min read