TM-13
Task Summary Suggests a User Story
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
Task issue with user-story format or outcome language in summary/description; tests; catalogue.
Detection formula
No published identification formula is available yet for this rule.Examples in practice
- A team shows task issue with user-story format or outcome language in summary/description; tests; catalogue during analysis.
- Example signal: Task issue with user-story format or outcome language in summary/description; tests; catalogue.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
The "Task Summary Suggests a User Story" signal shows a repeatable delivery anti-pattern on the cited issues.
Why it matters
When "Task Summary Suggests a User Story" 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 Summary Suggests a User Story" 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.