> For the complete documentation index, see [llms.txt](https://docs.oobeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s1-recurring-high-rework-rate.md). # S1- Recurring high rework rate ### **Why is this a symptom?** This symptom refers to a high rate of coding that needs to be redone or corrected. This could be due to a lack of clear requirements, inadequate testing, or a failure to follow established processes. Rework, by definition, wastes time and resources. A high rework rate is costly, time-consuming, and can cause delays, leading to frustration among team members. {% hint style="info" %} **Level:** Team Level **Potential Complications:** #low\_efficiency, #slow\_delivery, #dissatisfaction {% endhint %} ### **Possible Causes** * Lack of clear requirements * User stories with no clear Definition of Done * High technical debt & complexity, low-quality code * Lack of domain knowledge * Lack of knowledge-sharing culture * Inadequate testing * Failure to follow established processes ### **Improvement Areas** * Clarify requirements/user stories * Improve testing processes at the development level * Establish clear processes for analysis, development, and review * Provide additional training as needed * Review past instances of rework to identify patterns and root causes * Improve knowledge-sharing culture and practices within the team ### **Detection Method** Oobeya detects this symptom if the rework rate for recurring periods exceeds the specified threshold. **Formula:** (churn% > \[churn\_threshold]%) x\[specified\_period] recurring periods **Example:** During each of the **last 3 months**, the team has consistently had a **rework rate** of **more than 20%**. --- # 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, and the optional `goal` query parameter: ``` GET https://docs.oobeya.io/team-insights-and-symptoms/symptoms-catalog/s1-recurring-high-rework-rate.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.