Reports

• Velocity by sprints
• Velocity by releases
• Sprint burn down chart

Velocity by sprint

• total amount of the work in sprints
• state of the sprint stories and thus completeness status
• estimated maximum sprint velocity
• velocity for 3 worst sprints
• velocity for 8 last sprints
• maximum sprint velocity

Velocity by release

This chart provides releases status overview. Height of the column indicates total amount of the work needed to complete release. Product owner can easy identify release "price". Also, colored parts of the column indicates status of the release stories.

Sprint Burn Down chart

Burn down chart is a great agile way to know sprint status. This chart displays:

• Days of the sprint on x-axis
• Remaining work on y-axis
• Ideal progress of the work
• real work progress displaying amount of the work remaining in given sprint day

Sprint Burn Up chart

Another useful way of displaying sprint status is sprint Burn Up chart. This chart displays how much work has been completed since sprint start and how much work is planned for every sprint's day.

Parking lot

Parking lot report displays themes work status. For every theme is card created. Every card displays:

• theme name,
• count of the theme's stories
• number of completed story points for theme stories
• total number of story points for theme stories
• progress indicator with % of completeness

Sprint timesheet

This report displays sprint progress in a form of the time sheet. The time sheet is generated for all team members and selected sprint.

On a row are displayed stories and a tasks. The stories are displayed with yellow background.

Under a story's or task's name is displayed name of the team member who is working on given tasks. In second column is displayed duration estimated before the task starts. Following columns displays values entered in a given day by the team member.

In advance, for some values is displayed small arrow. Color of the arrow indicates exception of the estimated value.

Green arrow   indicates advance in a progress.

Red horizontal arrow indicates that in given days no progress has been recognized. This can indicate some unexpected problems with implementation or that the user doesn't update value.

Orange up arrow indicates that value has not decreased, but increased.

Values displayed with a gray color are values for other team member who participates on the given task.

Stories and tasks can be easy filtered by a click on the team member.  Multiple team members can be selected. Team members can be easy filtered by a filter text box in the right upper corner of the screen.

Sprint can be selected in a combo box from left top corner.

Detail of the story can be started by a double-click.

Daily Backlog Trend

Daily backlog trend displays effort changes in time during the product development. Sprints are displayed as small red filled circle.

User can easy identify when story points arise in time. Reasons for such change can be added stories or changed estimated effort of existing stories.

Stories by status

This chart displays distribution of stories by state. User is able to identify current backlog status.

See also:

• Planning screencast