> For the complete documentation index, see [llms.txt](https://typo.gitbook.io/typo-help-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://typo.gitbook.io/typo-help-docs/platform/health/metrics/flow.md).

# Flow

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

<div align="left"><figure><img src="/files/D3VhCi1UzyGWuiAsGdvQ" alt=""><figcaption></figcaption></figure></div>

The following metrics are part of velocity -

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

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](/typo-help-docs/engineering-metrics/pull-request-metrics/coding-time.md)

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

#### [Issue Cycle time](/typo-help-docs/engineering-metrics/sprint-metrics/issue-cycle-time.md)

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](/typo-help-docs/engineering-metrics/sprint-metrics/team-velocity.md)

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://typo.gitbook.io/typo-help-docs/platform/health/metrics/flow.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.