TM-05
Story Summary Suggests a Meeting or Process Event
Type Misclassification
Default severity: medium
Product BacklogPrioritizationQualityBusiness Value
What it detects
A Story or Feature has a summary suggesting a meeting, ceremony, event, or process administration item — these must never be tracked as stories. They have no delivery value, falsely inflate issue count, and corrupt all throughput and velocity metrics.
Detection formula
meeting_keywords = config.tm.meeting_keywords // defaults (EN): \[\'meeting\', \'standup\', \'stand-up\', \'retrospective\', \'retro\', \'planning\', \'refinement\', \'grooming\', \'demo\', \'review\', \'ceremony\', \'session\', \'workshop\', \'sync\', \'call\', \'discussion\', \'kickoff\', \'kick-off\', \'presentation\'\] // defaults (SK/CZ): \[\'stretnutie\', \'retrospektíva\', \'plánovanie\', \'refinement\', \'grooming\', \'demo\', \'prezentácia\', \'ceremónia\', \'diskusia\', \'workshop\', \'kickoff\'\] IF issue.type IN config.workflow.story_types AND summary MATCHES any(meeting_keywords) THEN CRITICAL — meetings must never be tracked as stories IF COUNT > 0 for team in current sprint THEN FLAG team for immediate correctionExamples in practice
- A team shows a story or feature has a summary suggesting a meeting, ceremony, event, or process administration item while meeting keywords is set to see 5l.2.
- Example signal: A Story or Feature has a summary suggesting a meeting, ceremony, event, or process administration item — these must never be tracked as stories.
Suggested response
Retype or rewrite summaries so issue types match the actual work described.
Coaching playbook
Symptom
A Story or Feature has a summary suggesting a meeting, ceremony, event, or process administration item — these must never be tracked as stories. They have no delivery value, falsely inflate issue count, and corrupt all throughput and velocity metrics.
Why it matters
When "Story Summary Suggests a Meeting or Process Event" 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 "Story Summary Suggests a Meeting or Process Event" 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.