WD-03
Analysis Logged as User Story
Work Definition
Default severity: high
Product BacklogEstimationProcessQuality
What it detects
Issues whose summary or description matches configured analysis/research keyword patterns are tracked as user stories — distorts velocity.
Detection formula
analysis_keywords = config.content.analysis_keywords // e.g. \[\'analyz\', \'research\', \'investigation\', \'spike\'\] IF issue.type IN config.workflow.story_types AND (summary OR description) MATCHES any(analysis_keywords) THEN WARNExamples in practice
- Work items enter active flow without the definition fields the team agreed on.
- Stories or features lack the metadata needed to verify readiness or completion.
- A team shows issues whose summary or description matches configured analysis/research keyword patterns are tracked as user stories while analysis keywords is set to Configured per workspace.
Suggested response
Bring acceptance criteria, sizing, and metadata in line with your definition of ready and done.
Coaching playbook
Symptom
Issues whose summary or description matches configured analysis/research keyword patterns are tracked as user stories — distorts velocity.
Why it matters
When "Analysis Logged as 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
Bring acceptance criteria, sizing, and metadata in line with your definition of ready and done.
Facilitation questions
- What system change would stop "Analysis Logged as 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.