TQ-19
Open Questions in Requirement Text
Text Quality
Default severity: high
ProcessMetrics
What it detects
Open questions, TBD, or unresolved placeholders remain in requirement text (Tabuľka 1 #10).
Detection formula
IF summary, description, or AC contains TBD, ?, or doriešiť cues THEN FLAGExamples in practice
- AC ends with TBD on error handling.
Suggested response
Resolve or assign each open question with owner and date before starting work.
Coaching playbook
Symptom
Open questions, TBD, or unresolved placeholders remain in requirement text (Tabuľka 1 #10).
Why it matters
When "Open Questions in Requirement Text" 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
Resolve or assign each open question with owner and date before starting work.
Facilitation questions
- What system change would stop "Open Questions in Requirement Text" 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.