Velocity Report

Keep a pulse on your sprint progress. Visualize and mitigate sprint risk using our forecast model. Identify capacity issues and scope creep.

The Velocity Report (former Sprints Report) provides a comprehensive view of your active sprints, enabling you to monitor sprint progress, identify capacity issues, and mitigate potential risks.

This report allows you to visualize the work being done by your team, including whether they are falling behind, whether they are over capacity, and whether there is any scope creep. The Velocity Report also offers a forecast model that can be used to identify and manage sprint risks.

Using the Velocity Report

This report displays all the issues that are inside the sprint, including stories, tasks, sub-tasks, bugs, and more. You can customize the mapping of these issues to suit your specific needs.

Within the Velocity Report, you can see the people assigned to each issue, any changes that are made to each issue, Pull Request and commit activity, issue cycle time, issue status, and risk.

Cycle Time is measured from the starting status of "Active" to the closing status of "Done."

Each commit is represented by a bubble in the Velocity Report. By clicking on any bubble, users can view a modal containing more information about the commit.

The modal contains who created that commit, the time it was created, the repository, and a link that redirects you to the commit page in the Git Provider. It also contains a work-focus distribution:

  • New Work - Brand new code that does not replace other code.

  • Legacy Refactor - The process of improving the structure of an old or unfamiliar code without changing its functionality (after 21 days)

  • Help others - It describes how much an engineer replaces another engineer's recent code - less than 21 days old.

  • Churn - Churn is when a developer re-writes their own code shortly after it has been checked in - less than 21 days old.

By monitoring this information, you can keep track of your sprint progress, identify any capacity issues, and take steps to mitigate any risks or issues that may arise.

Supported Methodologies

The Velocity Report supports both Scrum and Kanban methodologies.

When operating on a Scrum board, you have the additional option to select specific Sprints (from those that exist within the selected board.) Conversely, when navigating a Kanban board, the system provides access to the tickets.

To ensure clarity and ease of navigation, the Velocity Report automatically adjusts the page title to reflect your chosen board type. It accomplishes this by appending either "Scrum" or "Kanban" to the standard title.