# Developer Health ## Purpose This report gauges your developer team's health by comparing it to the industry benchmark on capacity. In particular, it provides insights into the PR load for teams and each team member over time. A high PR load means having PR tickets opened and juggled by a contributor simultaneously. This might lead to overloading the developer and poor outcomes due to the many parallel tasks. It can also slow the overall delivery because of context switching and delays. {% hint style="success" %} **Improvement Actions**: For overloaded teams or contributors can be helpful to redistribute some work, reduce the overall load, or add additional resourcing. Another aspect is ensuring smooth review and approval flows, as well as supportive infrastructure such as reliable and fast-build systems. {% endhint %} ## Explanations A team member is regarded as **overloaded** if he/she has more than a specific number of total PRs open at any given point in time. The default threshold is 5 PRs per week. **Overloaded Team:** The percentage of team members with too many PRs open at any given moment means they had too many parallel tasks. **Team PR Health:** The trend of development team health. It shows the percentage of the team members that were overloaded as a trend over time. High overloads for sustained periods of time indicate teams that might generally be under-resourced and are under sustained pressure. **Overloaded Developers**: Individual contributors who are currently deemed overloaded and have a history of their load. If a contributor has too much on for too long, they are at risk of suffering from burnout and productivity challenges affecting the whole team. ## Good to Know It is common that at certain times, specific contributors might have too many open PRs when waiting for reviews or fixes to the build system. However, if this affects large parts of the team, **productivity might be at risk,** leading to poor delivery results or high talent churn. --- # 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://docs.logilica.com/metrics-and-reports/code/developer-health.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.