TM-14
Team Task Overuse Ratio Exceeds Threshold
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
task share among delivery work units exceeds configurable threshold; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows task share among delivery work units exceeds configurable threshold; tests; catalogue during analysis.
- Example signal: task share among delivery work units exceeds configurable threshold; tests; catalogue.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
The "Team Task Overuse Ratio Exceeds Threshold" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Team Task Overuse Ratio Exceeds Threshold" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Retype or rewrite summaries so issue types match the actual work described.
Facilitation questions
- What system change would stop "Team Task Overuse Ratio Exceeds Threshold" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.