Agile (Scrum) Report

What are Agile Reports?

Agile Reports give you a holistic view of your sprint’s burn down, velocity and performance, and can help in retrospectives and better future sprint plannings.

Reports and Timesheets supports 3 Agile reports

1. Sprint Burndown - Shows the burn down data of current and completed sprints. Helps to see how a sprint progressed over time, scope additions and the completion rate of work.

2. Sprint Velocity - Shows the committed vs completed issues of selected sprints. Helps to estimate future velocity and plan commitment for new sprints.

3. Sprint Performance - Shows a detailed report of committed issues, net scope change in the committed, completed issues, remaining effort, scope additions and scope removal for a range of sprints. Helps to get a full view of a sprint’s planning based on the trend of net scope change over sprints and its effect on velocity.

How do I get started?

1. Click New report > Custom Report to open the Report Designer interface

2. Select page Type as Agile (Scrum)
   
   

   Open

   

3. The Agile Report Parameters filter displayed helps to select the type of report, the sprints the report needs to run for and the measure on which the report needs to be based.
   
   

   Open

   

    

4. Select the type of Agile Report. Options available :
   - Sprint Burndown
   - Sprint Velocity
   - Sprint Performance

5. Select the Board from the board selector. Note: Only non-Kanban boards are displayed.

6. On selecting board, sprints get displayed which are in open and closed statuses. Select the Sprint(s) for the selected report.
   Sprint Burn down report is for a single sprint and allows only a single sprint view. For Velocity and Performance reports, multiple sprints can be selected as shown below.

    

7. Select the Measure on which report needs to be based.
   Measure currently supports two criteria :

   • Story Points: Charts and the grids show the totals and issue wise data in story points

   • Issue Count: Charts and the grids show the totals and issue wise data in terms of count of issues

8. Click Run to view the results in the bottom pane. Sample burndown report below:

9. Click Export to export the results in Excel format

10. Click Save to save the report for future use. Saved reports can be accessed via My Area → My Reports.

11. For more options on Publishing a report with external users, Scheduling reports and Sharing report parameters, please refer to the My Area Overview.

How to use the reports?

Sprint Burn down Report

The Sprint burndown report shown below gives the below information:

1. Sprint name with the sprint start and end dates.

2. Sprint summary statistic shows the initial committed story points, the completed points with the % completion on committed. It also shows the net scope change during the sprint in story points

3. Burndown Chart shows the burndown over time. On hovering over markers on the chart, tooltips show the detailed change at that point of time.

4. Burndown Details shows the detailed changes in the sprint for all issues.
   - Event Detail column shows the event which caused to a story point change eg. Issue Added, Issue Removed, Issue Completed, Estimated added
   - Event Type indicates how it affected the sprint, eg caused a burndown, scope change
   
   

    

Sprint Velocity Report

The Sprint Velocity report shown below gives the below information:

1. Selected sprints for the Velocity data

2. Bars show the counts of Committed and Completed Measure based on the legend shown at top

3. Clicking on any of the bars gives the detailed report of the issues, which make up the sprint measure.
   In below sample, clicking on the Completed bar of Sprint 6, shows the Completed issues of the sprint, along with the story points.

Sprint Performance Report

The Sprint Performance report sampled below gives the below information:

1. Selected sprints for the Performance data

2. Legend - Legend allows to deselect any of the parameters that you chose not to see, clicking on the legend toggles the visibility of the data.

3. Bars:
   Committed - Total committed at the time of start of sprint
   Net Scope Change - Scope may be added or reduced based on issues added, removed, estimate changes. This bar shows how much scope was changed during the sprint,
   Completed - Shows the completed issues, which have not been reopened post completion in sprint.
   Remaining - Shows issues, if there were any remaining at the time of sprint closing
   Scope Added - Shows any scope that may be added post sprint start, due to new issue being added to sprint or due to estimate revision to a higher value
   Scope Reduced - Shows any scope that may be reduced post sprint start, due to issue being removed from sprint or due to estimate revision to a lower value
   
   

4. Clicking on any of the bars gives the detailed report of the issues, which make up the sprint measure.
   In below sample, clicking on the Scope Reduced bar of Sprint 3, shows the issues causing scope reduction in the sprint - Change event shows whether it was due to issue removal or estimate changes.