TM-15
Task vs Story Misuse
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
Description is not yet published for this rule in the PRD catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows description is not yet published for this rule in the prd catalogue during analysis.
- Example signal: Description is not yet published for this rule in the PRD catalogue.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
Description is not yet published for this rule in the PRD catalogue.
Why it matters
When "Task vs Story Misuse" 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 "Task vs Story Misuse" 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.