Track work progress
JIRA Software comes with a number of reports that will help everyone in your team understand the progress and success of their work. When you open your software project, select Reports (the 
icon) from your project sidebar. Follow along here for an introduction to some of the reports you and your team can use in a scrum project.
Track your team's velocity
Teams want to know what their velocity is. They want to know how accurately they are estimating and how much they are getting done each sprint in order to better estimate in future.
How to use the velocity chart
- See if your team is over-committing or under-committing to stories in sprint planning
- Check for outliers and drill into a sprint to learn form past mistakes (e.g. a grossly underestimated story)
- Monitor how velocity alters during periods of team change or growth
Lead successful sprints
Team leads (developer leads, technical leads, etc.) usually spend half their time thinking ahead to future work, and the other half firmly involved in the current sprint. They need to know how things are going now to help steer the team to a successful sprint completion.
How to use the burndown chart
- If the Remaining Value line it is headed straight across and not down, you need to find out why
- A successful sprint is where the Remaining Values line hits the bottom on or before the Guideline
- If the Remaining Value line ends before the guideline, you may have a bunch of overachievers or under-committers on your hands!
Manage projects and workload
Product managers (or project managers, depending on your structure) like to keep an eye on the bigger picture, so they can check if project milestones are being hit, where dev effort is being spent, and if the backlog is in need of a re-prioritization. The epic report is a good way to satisfying some of these demands.
How to use the epic report
- Easily see the how near or far an epic is from completion. Check with the team if things look unbalanced.
- Monitor issues that haven't been estimated. Chat to the dev lead to see if anything needs further clarification or breakdown.
