Reporting 1
To generate a report:
- Navigate to a board and select Reports. The last report viewed will display.
- Select Switch report to view a different report. The reports in this list are specific to agile development. Check the Reports for Scrum projects or Reports for Kanban projects sections in this document for more details.
- If you want to view reports that aren’t specific to agile development, select All reports from the Switch report dropdown and view the reports that aren’t in the Agile section.
Check the General reports for analyzing issues section in this document for more details.
Reports for Scrum projects
| Chart | Applies to | Purpose |
|---|---|---|
| Burndown Chart | Sprints | Tracks the total work remaining, and projects the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly. |
| Burnup Chart | Sprints | Tracks the changes in sprint scope and progress and helps visualize a sprint's completed work compared with its total scope. This helps your team understand what the progress is at each point of the release process or sprint. |
| Sprint Report | Sprints | Shows the work completed or pushed back to the backlog in each sprint. This helps you determine if your team is overcommitting or if there is scope creep. |
| Control Chart | Projects, versions, or sprints | Shows the cycle time for your product, version, or sprint. This helps you identify whether data from the current process can be used to determine future performance. |
| Cumulative Flow Diagram | Any period of time | Shows the statuses of issues over time. This helps you identify potential bottlenecks that need to be investigated. |
| Epic Report | Epics | Shows the progress towards completing an epic over time. This helps you manage your team's progress by tracking the remaining incomplete and unestimated work. |
| Epic Burndown | Epics | Similar to the Epic Report, but optimized for Scrum teams that work in sprints. Tracks the projected number of sprints required to complete the epic. This helps you monitor whether the epic will release on time, so you can take action if work is falling behind. |
| Release Burndown | Versions | Similar to the Version Report, but optimized for Scrum teams that work in sprints. Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind. |
| Velocity Chart | Sprints | Tracks the amount of work completed from sprint to sprint. This helps you determine your team's velocity, and estimate the work your team can realistically achieve in future sprints. |
| Version Report | Versions | Tracks the projected release date for a version. This helps you monitor whether the version will release on time, so you can take action if work is falling behind. |
Reports for Kanban projects
| Chart | Applies to | Purpose |
|---|---|---|
| Control Chart | Projects, versions, or sprints | Shows the cycle time for your product, version, or sprint. This helps you identify whether data from the current process can be used to determine future performance. |
| Cumulative Flow Diagram | Any period of time | Shows the statuses of issues over time. This helps you identify potential bottlenecks that need to be investigated. |