# Definitions - [Developer effort (FTEs)](https://help.swarmia.com/definitions/developer-effort-ftes.md): Learn how developer effort is measured in Swarmia - [DORA & deployment metrics](https://help.swarmia.com/definitions/dora-metrics.md) - [Change lead time](https://help.swarmia.com/definitions/dora-metrics/change-lead-time.md): Change lead time measures the full lifecycle of a pull request from the first commit to deployment. - [Time to deploy](https://help.swarmia.com/definitions/dora-metrics/time-to-deploy.md): Time to deploy is the average time between a pull request merge and deployment. - [Deployment frequency](https://help.swarmia.com/definitions/dora-metrics/deployment-frequency.md): Deployment frequency is calculated by looking at the total number of deployments that happened in a given time period. - [Mean time to recovery](https://help.swarmia.com/definitions/dora-metrics/mean-time-to-recovery.md): Mean time to recovery represents the average time between a failing deployment and a deployment that is marked as a fix. - [Change failure rate](https://help.swarmia.com/definitions/dora-metrics/change-failure-rate.md): Change failure rate is the ratio of failed deployments to all deployments. - [Throughput](https://help.swarmia.com/definitions/throughput.md): Throughput is defined as the number of pull requests you get through as a team over a selected period of time. - [Normalized throughput](https://help.swarmia.com/definitions/throughput/normalized-throughput.md): Normalizing issue or pull request throughput by active full-time equivalent developers helps make teams and time periods more comparable. - [Batch size](https://help.swarmia.com/definitions/batch-size.md): Batch size measures how much work is bundled up in a change. Swarmia offers tools for evaluating pull request batch size by looking at the total number of changes in a single pull request. - [Issue cycle time](https://help.swarmia.com/definitions/defining-issue-lifecycle-and-cycle-time.md): Issues progress through various stages of completeness during their lifetime. Swarmia automatically calculates key properties and metrics for each issue. - [Flow efficiency](https://help.swarmia.com/definitions/flow-efficiency.md): The flow efficiency of an issue is the percentage of days when the issue was actively worked on compared to its whole lifetime. - [Scope creep](https://help.swarmia.com/definitions/scope-creep.md): Scope creep measures the amount of work added to an issue while it was in progress. - [Definitions FAQ](https://help.swarmia.com/definitions/frequently-asked-questions.md) - [How do you treat weekends in metrics?](https://help.swarmia.com/definitions/frequently-asked-questions/how-do-you-treat-weekends-in-metrics.md) - [Tracking squashed commits](https://help.swarmia.com/definitions/frequently-asked-questions/tracking-squashed-commits.md): GitHub allows you to "squash" commits before merging a pull request. Swarmia supports this workflow. - [How do merge queues affect my metrics?](https://help.swarmia.com/definitions/frequently-asked-questions/how-do-merge-queues-affect-my-metrics.md): GitHub supports merging pull requests using a merge queue. This doesn't affect the definitions of cycle time or DORA metrics. - [Why is my commit not visible in Swarmia?](https://help.swarmia.com/definitions/frequently-asked-questions/why-is-my-commit-not-visible-in-swarmia.md): We include only commits from pull requests. Check that the pull request is visible in Swarmia. - [What happens when people switch teams or leave?](https://help.swarmia.com/definitions/frequently-asked-questions/how-do-i-account-for-people-leaving-my-organization.md): Swarmia tracks the historical team memberships of contributors over time. Contributions made for one team will stay correctly attributed, even if their author later switches teams or leaves. - [How do I configure Swarmia if I use the Gitflow branching strategy?](https://help.swarmia.com/definitions/frequently-asked-questions/how-do-i-configure-swarmia-if-i-use-the-gitflow-branching-strategy.md) --- # Agent Instructions: 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://help.swarmia.com/definitions.md?ask= ``` 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.