Track success. Optimize the rest.
Zenhub’s agile reports track issue progress to give you insights into your team’s capacity, goal progress, work habits, bottlenecks, and everything you need to optimize success.
Real-time, ready-to-view reports
Zenhub automatically creates agile reports based on your team's activities in GitHub, with no configuration required. Action insights based on your team’s progress, challenges, and capacity.
Get visibility into
how your team works
Increase project
predictability
Instant GitHub
repository insights
Get visibility into how your team works
Increase project predictability
Instant GitHub repository insights
What our customers are saying
“Zenhub gave us the capability to have a single workflow with minimal overhead and integration with different GitHub contexts, not to mention much better reporting and planning features than were available elsewhere.”
Why software teams love our reports
For developers
For product leaders
Explore other features
Boards
Sprint planning
Roadmaps
Workflow automation
Planning poker
Zenhub extension
Key terms and concepts to know
“Pipelines,” on a Kanban (or Agile/Scrum) board, represent the status of the work being done. For example, “In review” may be a status. In agile reporting, how much time an issue spends in a pipeline can give insight into inefficient processes.
“Issues” in agile project management are another word for smaller tasks or individual units of work. In Zenhub, issues best suited to developers are GitHub Issues and issues best suited to non-technical team members are Zenhub Issues.
Velocity tracks the average amount of story points your team completes per sprint and averages them over time to calculate “velocity,” which is the average capacity your team has across multiple sprints.
Sprints, in agile project management, are defined periods of time in which a software team commits to an assigned group of issues to work on. Sprints are usually 2-4 weeks long.
Burndown Charts are scatterplots that graph the number of story points your team completes over a sprint. The date is displayed on the X axis, and the # of story points is on the Y axis. The chart cascades or “burns” downwards as story points are completed.
Release reports are similar to Burndown Charts in their ability to show the progress of projects. Release Report scatterplots are displayed as moving upward as your team makes progress, making it easier to understand the scope of a project and predict project end dates.
Cumulative flow charts are graphs that display the number of issues within each given pipeline over a period of time. Cumulative Flow charts are useful for understanding where your team is most efficient and what processes are the biggest blockers.
Control charts track lead and cycle time. This is the amount of time it takes from creating an issue to closing it and merging a PR. Control charts are useful for estimating how long tasks will take when managing clients and leadership expectations.
Frequently asked questions
What reports does Zenhub include?
There are 5 key reports in Zenhub’s reporting suite: Burndown Reports, Velocity Tracking, Control Charts, Release Reports, and Cumulative Flow.
What metrics does Zenhub track?
Key metrics Zenhub tracks:
• Total # of issues closed vs. remaining
• Total # of story points completed vs. planned
• Total # of pull requests merged vs. remaining
• Lead/Cycle time
• Average velocity across all sprints
• # of story points completed for each individual sprint
What do I have to do to create reports in Zenhub?
Zenhub creates reports for you automatically, so you don’t need to create them manually. However, there is some data we’ll need to create reports for you. For Cumulative Flow charts, Release Reports, and Control Charts, you just need to be regularly creating and closing issues inside Zenhub. For Burndown Reports and Velocity tracking, you will need to use Zenhub Sprints so that we can calculate sprint-related data.
Need more help?
