TM-09
Systemic Misclassification Pattern — Team-Level
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
A team has a systematic pattern of issue type misclassification across multiple rules (TM-01 through TM-08) — more than the configured percentage of their stories trigger at least one type signal. This indicates a team-wide deficit in backlog grooming, story writing training, or Scrum Master oversight.
Detection formula
FOR each_team T: misclassified_stories(T) = COUNT(stories WHERE any TM-01..08 fired) misclassification_rate(T) = misclassified_stories(T) / COUNT(all_stories, team=T) IF misclassification_rate(T) > config.tm.systemic_threshold // default: 0.25 (25% of stories misclassified) THEN FLAG systemic_misclassification for team T Report: breakdown by TM rule — which misclassification types dominate Recommended action: backlog health workshop with Scrum MasterExamples in practice
- A team shows a team has a systematic pattern of issue type misclassification across multiple rules (tm-01 through tm-08) while systemic threshold is set to 0.25 (25% of stories misclassified).
- Example signal: A team has a systematic pattern of issue type misclassification across multiple rules (TM-01 through TM-08) — more than the configured percentage of their stories trigger at least one type signal.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
A team has a systematic pattern of issue type misclassification across multiple rules (TM-01 through TM-08) — more than the configured percentage of their stories trigger at least one type signal. This indicates a team-wide deficit in backlog grooming, story writing training, or Scrum Master oversight.
Why it matters
When "Systemic Misclassification Pattern — Team-Level" 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 "Systemic Misclassification Pattern — Team-Level" 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.