The document discusses different reports that various roles in an agile project may find useful. It describes the Sprint Burndown report that team members typically view to track progress towards completing sprint work. It also outlines reports helpful for Scrum Masters, such as the Sprint Dashboard that shows task estimates and member workload. Product Owners are said to benefit from the Project Dashboard and Burndown, Total Estimate Trend, and Velocity Trend reports. Stakeholders can get a program-level summary from the Project/Program Summary report.

1. VersionOne
Basic Reports

2. © 2010 VersionOne, Inc. 2
Not all people look at the same reports
What report should I be looking at?
Who am I/What is my role?
How do I interpret the reports?
It this data enough for the big picture?
How often should I look at reports?
Depends on what you are looking at and why.

3. © 2010 VersionOne, Inc. 3
Team Member Reports
The most significant report a team member looks at is typically the Sprint
Burndown. It is important for all team members to burn down the remaining
work to do so that the team has transparency into their progress.
The Sprint burndown will display the actual remaining work todo and
compare it to an ideal line to show progress. In this case, the last data point
is below the ideal line, which indicates that the team is ahead of schedule to
complete all of the work for this Sprint.

4. © 2010 VersionOne, Inc. 4
Scrum Master Reports
A Scrum Masters role in the team is to help facilitate meetings and information and to
remove impediments. Having said that, what information is helpful for a SM to be able to
identify potential issues?
The Sprint Dashboard offers several points of interest that help in putting together a better
picture of what is happening. We’ve covered the Burndown, so now lets look at the Trend-
Total Detailed Estimate:

5. © 2010 VersionOne, Inc. 5
The Total Detailed Estimate Trend helps
Understand how effort is trending
compared to the detail estimated
entered in to the tasks and tests.
The Total Estimate Trend measures
the scope of the Sprint and ‘burns
up” as backlog items are closed.
So, here we can see that there has
been an increase in scope the third
day into this sprint.
Scrum Master Reports

6. © 2010 VersionOne, Inc. 6
Scrum Master Reports
The Current Member Load displays each members’ workload in terms of hours and breaks
done between done and remaining to do. Included in the Sprint Dashboard is also a Current
Member Load Across Projects which will help the team understand how the work for this
project impacts a persons total workload.

7. © 2010 VersionOne, Inc. 7
The Member Tracking grid is something that I would be looking at daily as a
Scrum Master. This report shows the total detailed estimate compared to the
total capacity, which lets the team know immediately if they are over
allocated. Additionally, this report show, on an individual level, how one
person’s under/over allocation of work can impact the team’s ability to
complete their commitment.
Scrum Master Reports
This report is useful
if capacity planning
is being utilized.

8. © 2010 VersionOne, Inc. 8
The Project Dashboard is a favorite among Product Owners. This report allows
for configurable dates and can be filtered by teams.
Product Owner Reports

9. © 2010 VersionOne, Inc. 9
The Project Burndown displays the remaining estimate (scope) comparative to
the ideal line for the project. Each data point can be moused over to display
exactly hove my scope is remaining. Each time a backlog item is closed, the
Open Estimate line will reduce.
Product Owner Reports

10. © 2010 VersionOne, Inc. 10
The Total Estimate Trend displays the scope of the project as it is added or
removed. The grey (closed Estimate) parts of each column represents the
backlog items being closed during the timeframe indicated on the
parameters of this report. Many people consider the report the “burn-up”
report
Product Owner Reports

11. © 2010 VersionOne, Inc. 11
The Velocity Trend offers visibility in a stable (or instable) velocity. Having a
consistent velocity allows for more predictable planning for both the team
and the Product Owner.
Product Owner Reports

12. © 2010 VersionOne, Inc. 12
Product Owner Reports
Test Count By Status display a burndown of failed vs passed tests throughout the
project. We typically see the test count increase over time, but we also want to see
more and more passed tests as opposed to failed tests.

13. © 2010 VersionOne, Inc. 13
Stakeholder Reports
The Project/Program Summary gives a quick comparative view of how the scope of work
is moving towards completion for all of the projects. The red dotted line indicates today
in order to give perspective of how the project is progressing.

14. © 2010 VersionOne, Inc. 14
Questions