Velocity is the total number of story points associated with completed tickets.
In this article
Which reports use Velocity?
See Velocity in Metrics overview, Retrospective, and Check-in.
See the story points associated with each ticket in Sprint movement and Ticket log.
What does Velocity measure?
Velocity helps you understand the throughput of your team by measuring how many story points were associated with completed tickets. While this is not a comprehensive measure of the quantity of work you're completing, it's a useful metric to help you understand your throughput patterns, especially if your teams share a strategy for assigning story points to tickets.
How is Velocity calculated?
Velocity is the total number of story points associated with tickets that moved to their final Done status during the selected time frame.
Note: If a ticket previously in a Done status moves to a new Done status, the completion date for the ticket updates to the date of the most recent Done status, and the story points associated with the ticket are removed from any previous Velocity counts.
What data is included in Velocity?
Note: To calculate Velocity correctly, Flow needs to access the field that stores your story point information. Flow uses these fields by default. If you use a custom field for your story point information, set up custom mapping for story points in your ticket project configuration. Typically, velocity will show as zero if you need to update your story point mapping.
Tickets are included in Velocity if:
- They are in a Done status according to the ticket project configurations
- They were moved to their most recent Done state during the selected time frame
- The selected user or a member of the selected team was an assignee on the ticket at any point after it moved into its first Active status
Tickets are not included in Velocity if:
- They are in a Canceled status
- They have not been moved to a Done status or were not moved to a Done status in the selected date range
- The selected user or a member of the selected team was never an assignee on the ticket or was only an assignee in an In progress status
- They were moved to a different Done state after the selected date range
- Their issue type is excluded as part of ticket type assignment in the ticket project configurations