# Flow

Measures the speed and efficiency at which developers deliver features or complete tasks. 

<div align="left"><figure><img src="https://813988662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeCZyG1kSmV84geZ9Ws6s%2Fuploads%2FzJMpfzI8YrUHWUJVOyu7%2FScreenshot%202025-06-03%20at%2012.34.10%E2%80%AFAM.png?alt=media&#x26;token=0305a8a3-0de9-4cc2-9f33-1f8975e6d941" alt=""><figcaption></figcaption></figure></div>

The following metrics are part of velocity -

#### [PR Cycle Time](https://typo.gitbook.io/typo-help-docs/engineering-metrics/dora/pr-cycle-time)

The cycle time is the average duration that Pull requests spend in different stages of the pipeline, including "**Coding**," "**Pickup**," "**Review**," and "**Merge.**"

#### [Coding time](https://typo.gitbook.io/typo-help-docs/engineering-metrics/pull-request-metrics/coding-time)

The "Coding" stage represents the average time taken by developers to write and commit the code changes.

#### [Issue Cycle time](https://typo.gitbook.io/typo-help-docs/engineering-metrics/sprint-metrics/issue-cycle-time)

Issue Cycle Time represents the average time it takes for an Issue ticket to transition from the 'In Progress' state to the 'Completion' state.

#### [Issue Velocity](https://typo.gitbook.io/typo-help-docs/engineering-metrics/sprint-metrics/team-velocity)

Issue velocity represents the average number of completed tickets by a team in the selected period.