Rules
| Title | Rule | Problem | Categories |
|---|---|---|---|
| Status change without reason | If a task changes status without a comment - write to the author asking to clarify the purpose of the move. | Poor transparency in the development process. | Task execution control, Process transparency |
| Risky ticket | If a task stays in one status for more than 3 days - send a warning to the chat. | Weak control of dependent tasks. | Risk management, Task execution control |
| Knowledge base enrichment | After closing a bug task - add its description and solution to the knowledge base. | Repeating errors and lack of history. | Knowledge management, Retrospectives and improvements |
| Overload warning | If a user has more than 5 tasks in progress - notify the manager. | Employee overload. | Workload and focus management, Efficiency and metrics |
| Unrealistic estimation | If a task is estimated at less than 1 hour or more than 40 - ask for clarification. | Poor planning. | Planning and estimation, Task execution control |
| Unclear goal | If task description is < 10 words - mark as requiring refinement. | Incomplete task formulation. | Requirements and goals alignment, Value and customer orientation |
| Sprint forecast | Every morning send a forecast of task completion for the current sprint. | Lack of progress control. | Planning and estimation, Task execution control |
| Invisible PR | If MR hangs without comments >24 hours - tag reviewer <username>. | Review delay. | Process transparency, Development and testing quality |
| Who forgot about the task? | If a task is in Waiting QA >2 days - remind QA <username>. | Lost tasks. | Task execution control, Process transparency |
| Unknown assignee | If a task has no assignee - comment asking to assign. | Task non-completion. | Process transparency, Task execution control |
Showing 1-10 of 20 Rules
1 of 2